Uplink Control Information in Unlicensed Bands in a Wireless Network

ABSTRACT

A wireless device receives configuration parameters of periodic radio resources of a configured uplink grant. The periodic radio resources comprise: one or more first resource elements of a first sub-band; and one or more second resource elements of a second sub-band. The wireless device multiplexes: a first configured grant uplink control information (CG-UCI) via the one or more first resource elements; and a second CG-UCI via the one or more second resource elements. The second CG-UCI is be based on a repetition of the first CG-UCI. At least one of the first CG-UCI and the second CG-UCI is transmitted via the periodic radio resources and based on one or more listen-before-talk (LBT) procedures performed on the first sub-band and the second sub-band.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No.62/910,266, filed Oct. 3, 2019, which is hereby incorporated byreference in its entirety.

BRIEF DESCRIPTION OF THE DRAWINGS

Examples of several of the various embodiments of the present disclosureare described herein with reference to the drawings.

FIG. 1A and FIG. 1B illustrate example mobile communication networks inwhich embodiments of the present disclosure may be implemented.

FIG. 2A and FIG. 2B respectively illustrate a New Radio (NR) user planeand control plane protocol stack.

FIG. 3 illustrates an example of services provided between protocollayers of the NR user plane protocol stack of FIG. 2A.

FIG. 4A illustrates an example downlink data flow through the NR userplane protocol stack of FIG. 2A.

FIG. 4B illustrates an example format of a MAC subheader in a MAC PDU.

FIG. 5A and FIG. 5B respectively illustrate a mapping between logicalchannels, transport channels, and physical channels for the downlink anduplink.

FIG. 6 is an example diagram showing RRC state transitions of a UE.

FIG. 7 illustrates an example configuration of an NR frame into whichOFDM symbols are grouped.

FIG. 8 illustrates an example configuration of a slot in the time andfrequency domain for an NR carrier.

FIG. 9 illustrates an example of bandwidth adaptation using threeconfigured BWPs for an NR carrier.

FIG. 10A illustrates three carrier aggregation configurations with twocomponent carriers.

FIG. 10B illustrates an example of how aggregated cells may beconfigured into one or more PUCCH groups.

FIG. 11A illustrates an example of an SS/PBCH block structure andlocation.

FIG. 11B illustrates an example of CSI-RSs that are mapped in the timeand frequency domains.

FIG. 12A and FIG. 12B respectively illustrate examples of three downlinkand uplink beam management procedures.

FIG. 13A, FIG. 13B, and FIG. 13C respectively illustrate a four-stepcontention-based random access procedure, a two-step contention-freerandom access procedure, and another two-step random access procedure.

FIG. 14A illustrates an example of CORESET configurations for abandwidth part.

FIG. 14B illustrates an example of a CCE-to-REG mapping for DCItransmission on a CORESET and PDCCH processing.

FIG. 15 illustrates an example of a wireless device in communicationwith a base station.

FIG. 16A, FIG. 16B, FIG. 16C, and FIG. 16D illustrate example structuresfor uplink and downlink transmission.

FIG. 17 illustrates an example of UCI mapping in CG PUSCH for NR-Uconfigured grant transmission as per an aspect of an example embodimentof the present disclosure.

FIG. 18 illustrates example allocation of a resource to multiplewireless devices with different starting points as per an aspect of anexample embodiment of the present disclosure.

FIG. 19 illustrates example allocation of a resource to multiplewireless devices with different frequency divisions as per an aspect ofan example embodiment of the present disclosure.

FIG. 20 illustrates example mapping of CG-UCI in a same CG resource fordifferent wireless device as per an aspect of an example embodiment ofthe present disclosure.

FIG. 21 illustrates example mapping of CG-UCI in a same CG resource fordifferent wireless device based on interlacing as per an aspect of anexample embodiment of the present disclosure.

FIG. 22 illustrates example mapping of CG-UCI to a LBT subband in awideband configured grant as per an aspect of an example embodiment ofthe present disclosure.

FIG. 23 illustrates an example multiplexing of CG-UCI on different LBTsubbands based on LBT result(s) as per an aspect of an exampleembodiment of the present disclosure.

FIG. 24 illustrates an example mapping of CG-UCI repeatedly on multipleLBT subbands of a wideband configured grant as per an aspect of anexample embodiment of the present disclosure.

FIG. 25 illustrates an example mapping of CG-UCI on multiple LBTsubbands of a wideband configured grant with different frequencyoffset(s) and/or different number of PRBs as per an aspect of an exampleembodiment of the present disclosure.

FIG. 26 illustrates an example mapping of CG-UCI on multiple LBTsubbands of a wideband configured grant using interleaving as per anaspect of an example embodiment of the present disclosure.

FIG. 27 is a flow diagram of an aspect of an example embodiment of thepresent disclosure.

DETAILED DESCRIPTION

In the present disclosure, various embodiments are presented as examplesof how the disclosed techniques may be implemented and/or how thedisclosed techniques may be practiced in environments and scenarios. Itwill be apparent to persons skilled in the relevant art that variouschanges in form and detail can be made therein without departing fromthe scope. In fact, after reading the description, it will be apparentto one skilled in the relevant art how to implement alternativeembodiments. The present embodiments should not be limited by any of thedescribed exemplary embodiments. The embodiments of the presentdisclosure will be described with reference to the accompanyingdrawings. Limitations, features, and/or elements from the disclosedexample embodiments may be combined to create further embodiments withinthe scope of the disclosure. Any figures which highlight thefunctionality and advantages, are presented for example purposes only.The disclosed architecture is sufficiently flexible and configurable,such that it may be utilized in ways other than that shown. For example,the actions listed in any flowchart may be re-ordered or only optionallyused in some embodiments.

Embodiments may be configured to operate as needed. The disclosedmechanism may be performed when certain criteria are met, for example,in a wireless device, a base station, a radio environment, a network, acombination of the above, and/or the like. Example criteria may bebased, at least in part, on for example, wireless device or network nodeconfigurations, traffic load, initial system set up, packet sizes,traffic characteristics, a combination of the above, and/or the like.When the one or more criteria are met, various example embodiments maybe applied. Therefore, it may be possible to implement exampleembodiments that selectively implement disclosed protocols.

A base station may communicate with a mix of wireless devices. Wirelessdevices and/or base stations may support multiple technologies, and/ormultiple releases of the same technology. Wireless devices may have somespecific capability(ies) depending on wireless device category and/orcapability(ies). When this disclosure refers to a base stationcommunicating with a plurality of wireless devices, this disclosure mayrefer to a subset of the total wireless devices in a coverage area. Thisdisclosure may refer to, for example, a plurality of wireless devices ofa given LTE or 5G release with a given capability and in a given sectorof the base station. The plurality of wireless devices in thisdisclosure may refer to a selected plurality of wireless devices, and/ora subset of total wireless devices in a coverage area which performaccording to disclosed methods, and/or the like. There may be aplurality of base stations or a plurality of wireless devices in acoverage area that may not comply with the disclosed methods, forexample, those wireless devices or base stations may perform based onolder releases of LTE or 5G technology.

In this disclosure, “a” and “an” and similar phrases are to beinterpreted as “at least one” and “one or more.” Similarly, any termthat ends with the suffix “(s)” is to be interpreted as “at least one”and “one or more.” In this disclosure, the term “may” is to beinterpreted as “may, for example.” In other words, the term “may” isindicative that the phrase following the term “may” is an example of oneof a multitude of suitable possibilities that may, or may not, beemployed by one or more of the various embodiments. The terms“comprises” and “consists of”, as used herein, enumerate one or morecomponents of the element being described. The term “comprises” isinterchangeable with “includes” and does not exclude unenumeratedcomponents from being included in the element being described. Bycontrast, “consists of” provides a complete enumeration of the one ormore components of the element being described. The term “based on”, asused herein, should be interpreted as “based at least in part on” ratherthan, for example, “based solely on”. The term “and/or” as used hereinrepresents any possible combination of enumerated elements. For example,“A, B, and/or C” may represent A; B; C; A and B; A and C; B and C; or A,B, and C.

If A and B are sets and every element of A is an element of B, A iscalled a subset of B. In this specification, only non-empty sets andsubsets are considered. For example, possible subsets of B={cell1,cell2} are: {cell1}, {cell2}, and {cell1, cell2}. The phrase “based on”(or equally “based at least on”) is indicative that the phrase followingthe term “based on” is an example of one of a multitude of suitablepossibilities that may, or may not, be employed to one or more of thevarious embodiments. The phrase “in response to” (or equally “inresponse at least to”) is indicative that the phrase following thephrase “in response to” is an example of one of a multitude of suitablepossibilities that may, or may not, be employed to one or more of thevarious embodiments. The phrase “depending on” (or equally “depending atleast to”) is indicative that the phrase following the phrase “dependingon” is an example of one of a multitude of suitable possibilities thatmay, or may not, be employed to one or more of the various embodiments.The phrase “employing/using” (or equally “employing/using at least”) isindicative that the phrase following the phrase “employing/using” is anexample of one of a multitude of suitable possibilities that may, or maynot, be employed to one or more of the various embodiments.

The term configured may relate to the capacity of a device whether thedevice is in an operational or non-operational state. Configured mayrefer to specific settings in a device that effect the operationalcharacteristics of the device whether the device is in an operational ornon-operational state. In other words, the hardware, software, firmware,registers, memory values, and/or the like may be “configured” within adevice, whether the device is in an operational or nonoperational state,to provide the device with specific characteristics. Terms such as “acontrol message to cause in a device” may mean that a control messagehas parameters that may be used to configure specific characteristics ormay be used to implement certain actions in the device, whether thedevice is in an operational or non-operational state.

In this disclosure, parameters (or equally called, fields, orInformation elements: IEs) may comprise one or more information objects,and an information object may comprise one or more other objects. Forexample, if parameter (IE) N comprises parameter (IE) M, and parameter(IE) M comprises parameter (IE) K, and parameter (IE) K comprisesparameter (information element) J. Then, for example, N comprises K, andN comprises J. In an example embodiment, when one or more messagescomprise a plurality of parameters, it implies that a parameter in theplurality of parameters is in at least one of the one or more messages,but does not have to be in each of the one or more messages.

Many features presented are described as being optional through the useof “may” or the use of parentheses. For the sake of brevity andlegibility, the present disclosure does not explicitly recite each andevery permutation that may be obtained by choosing from the set ofoptional features. The present disclosure is to be interpreted asexplicitly disclosing all such permutations. For example, a systemdescribed as having three optional features may be embodied in sevenways, namely with just one of the three possible features, with any twoof the three possible features or with three of the three possiblefeatures.

Many of the elements described in the disclosed embodiments may beimplemented as modules. A module is defined here as an element thatperforms a defined function and has a defined interface to otherelements. The modules described in this disclosure may be implemented inhardware, software in combination with hardware, firmware, wetware (e.g.hardware with a biological element) or a combination thereof, which maybe behaviorally equivalent. For example, modules may be implemented as asoftware routine written in a computer language configured to beexecuted by a hardware machine (such as C, C++, Fortran, Java, Basic,Matlab or the like) or a modeling/simulation program such as Simulink,Stateflow, GNU Octave, or Lab VIEWMathScript. It may be possible toimplement modules using physical hardware that incorporates discrete orprogrammable analog, digital and/or quantum hardware. Examples ofprogrammable hardware comprise: computers, microcontrollers,microprocessors, application-specific integrated circuits (ASICs); fieldprogrammable gate arrays (FPGAs); and complex programmable logic devices(CPLDs). Computers, microcontrollers and microprocessors are programmedusing languages such as assembly, C, C++ or the like. FPGAs, ASICs andCPLDs are often programmed using hardware description languages (HDL)such as VHSIC hardware description language (VHDL) or Verilog thatconfigure connections between internal hardware modules with lesserfunctionality on a programmable device. The mentioned technologies areoften used in combination to achieve the result of a functional module.

FIG. 1A illustrates an example of a mobile communication network 100 inwhich embodiments of the present disclosure may be implemented. Themobile communication network 100 may be, for example, a public landmobile network (PLMN) run by a network operator. As illustrated in FIG.1A, the mobile communication network 100 includes a core network (CN)102, a radio access network (RAN) 104, and a wireless device 106.

The CN 102 may provide the wireless device 106 with an interface to oneor more data networks (DNs), such as public DNs (e.g., the Internet),private DNs, and/or intra-operator DNs. As part of the interfacefunctionality, the CN 102 may set up end-to-end connections between thewireless device 106 and the one or more DNs, authenticate the wirelessdevice 106, and provide charging functionality.

The RAN 104 may connect the CN 102 to the wireless device 106 throughradio communications over an air interface. As part of the radiocommunications, the RAN 104 may provide scheduling, radio resourcemanagement, and retransmission protocols. The communication directionfrom the RAN 104 to the wireless device 106 over the air interface isknown as the downlink and the communication direction from the wirelessdevice 106 to the RAN 104 over the air interface is known as the uplink.Downlink transmissions may be separated from uplink transmissions usingfrequency division duplexing (FDD), time-division duplexing (TDD),and/or some combination of the two duplexing techniques.

The term wireless device may be used throughout this disclosure to referto and encompass any mobile device or fixed (non-mobile) device forwhich wireless communication is needed or usable. For example, awireless device may be a telephone, smart phone, tablet, computer,laptop, sensor, meter, wearable device, Internet of Things (IoT) device,vehicle road side unit (RSU), relay node, automobile, and/or anycombination thereof. The term wireless device encompasses otherterminology, including user equipment (UE), user terminal (UT), accessterminal (AT), mobile station, handset, wireless transmit and receiveunit (WTRU), and/or wireless communication device.

The RAN 104 may include one or more base stations (not shown). The termbase station may be used throughout this disclosure to refer to andencompass a Node B (associated with UMTS and/or 3G standards), anEvolved Node B (eNB, associated with E-UTRA and/or 4G standards), aremote radio head (RRH), a baseband processing unit coupled to one ormore RRHs, a repeater node or relay node used to extend the coveragearea of a donor node, a Next Generation Evolved Node B (ng-eNB), aGeneration Node B (gNB, associated with NR and/or 5G standards), anaccess point (AP, associated with, for example, WiFi or any othersuitable wireless communication standard), and/or any combinationthereof. A base station may comprise at least one gNB Central Unit(gNB-CU) and at least one a gNB Distributed Unit (gNB-DU).

A base station included in the RAN 104 may include one or more sets ofantennas for communicating with the wireless device 106 over the airinterface. For example, one or more of the base stations may includethree sets of antennas to respectively control three cells (or sectors).The size of a cell may be determined by a range at which a receiver(e.g., a base station receiver) can successfully receive thetransmissions from a transmitter (e.g., a wireless device transmitter)operating in the cell. Together, the cells of the base stations mayprovide radio coverage to the wireless device 106 over a wide geographicarea to support wireless device mobility.

In addition to three-sector sites, other implementations of basestations are possible. For example, one or more of the base stations inthe RAN 104 may be implemented as a sectored site with more or less thanthree sectors. One or more of the base stations in the RAN 104 may beimplemented as an access point, as a baseband processing unit coupled toseveral remote radio heads (RRHs), and/or as a repeater or relay nodeused to extend the coverage area of a donor node. A baseband processingunit coupled to RRHs may be part of a centralized or cloud RANarchitecture, where the baseband processing unit may be eithercentralized in a pool of baseband processing units or virtualized. Arepeater node may amplify and rebroadcast a radio signal received from adonor node. A relay node may perform the same/similar functions as arepeater node but may decode the radio signal received from the donornode to remove noise before amplifying and rebroadcasting the radiosignal.

The RAN 104 may be deployed as a homogenous network of macrocell basestations that have similar antenna patterns and similar high-leveltransmit powers. The RAN 104 may be deployed as a heterogeneous network.In heterogeneous networks, small cell base stations may be used toprovide small coverage areas, for example, coverage areas that overlapwith the comparatively larger coverage areas provided by macrocell basestations. The small coverage areas may be provided in areas with highdata traffic (or so-called “hotspots”) or in areas with weak macrocellcoverage. Examples of small cell base stations include, in order ofdecreasing coverage area, microcell base stations, picocell basestations, and femtocell base stations or home base stations.

The Third-Generation Partnership Project (3GPP) was formed in 1998 toprovide global standardization of specifications for mobilecommunication networks similar to the mobile communication network 100in FIG. 1A. To date, 3GPP has produced specifications for threegenerations of mobile networks: a third generation (3G) network known asUniversal Mobile Telecommunications System (UMTS), a fourth generation(4G) network known as Long-Term Evolution (LTE), and a fifth generation(5G) network known as 5G System (5GS). Embodiments of the presentdisclosure are described with reference to the RAN of a 3GPP 5G network,referred to as next-generation RAN (NG-RAN). Embodiments may beapplicable to RANs of other mobile communication networks, such as theRAN 104 in FIG. 1A, the RANs of earlier 3G and 4G networks, and those offuture networks yet to be specified (e.g., a 3GPP 6G network). NG-RANimplements 5G radio access technology known as New Radio (NR) and may beprovisioned to implement 4G radio access technology or other radioaccess technologies, including non-3GPP radio access technologies.

FIG. 1B illustrates another example mobile communication network 150 inwhich embodiments of the present disclosure may be implemented. Mobilecommunication network 150 may be, for example, a PLMN run by a networkoperator. As illustrated in FIG. 1B, mobile communication network 150includes a 5G core network (5G-CN) 152, an NG-RAN 154, and UEs 156A and156B (collectively UEs 156). These components may be implemented andoperate in the same or similar manner as corresponding componentsdescribed with respect to FIG. 1A.

The 5G-CN 152 provides the UEs 156 with an interface to one or more DNs,such as public DNs (e.g., the Internet), private DNs, and/orintra-operator DNs. As part of the interface functionality, the 5G-CN152 may set up end-to-end connections between the UEs 156 and the one ormore DNs, authenticate the UEs 156, and provide charging functionality.Compared to the CN of a 3GPP 4G network, the basis of the 5G-CN 152 maybe a service-based architecture. This means that the architecture of thenodes making up the 5G-CN 152 may be defined as network functions thatoffer services via interfaces to other network functions. The networkfunctions of the 5G-CN 152 may be implemented in several ways, includingas network elements on dedicated or shared hardware, as softwareinstances running on dedicated or shared hardware, or as virtualizedfunctions instantiated on a platform (e.g., a cloud-based platform).

As illustrated in FIG. 1B, the 5G-CN 152 includes an Access and MobilityManagement Function (AMF) 158A and a User Plane Function (UPF) 158B,which are shown as one component AMF/UPF 158 in FIG. 1B for ease ofillustration. The UPF 158B may serve as a gateway between the NG-RAN 154and the one or more DNs. The UPF 158B may perform functions such aspacket routing and forwarding, packet inspection and user plane policyrule enforcement, traffic usage reporting, uplink classification tosupport routing of traffic flows to the one or more DNs, quality ofservice (QoS) handling for the user plane (e.g., packet filtering,gating, uplink/downlink rate enforcement, and uplink trafficverification), downlink packet buffering, and downlink data notificationtriggering. The UPF 158B may serve as an anchor point forintra-/inter-Radio Access Technology (RAT) mobility, an externalprotocol (or packet) data unit (PDU) session point of interconnect tothe one or more DNs, and/or a branching point to support a multi-homedPDU session. The UEs 156 may be configured to receive services through aPDU session, which is a logical connection between a UE and a DN.

The AMF 158A may perform functions such as Non-Access Stratum (NAS)signaling termination, NAS signaling security, Access Stratum (AS)security control, inter-CN node signaling for mobility between 3GPPaccess networks, idle mode UE reachability (e.g., control and executionof paging retransmission), registration area management, intra-systemand inter-system mobility support, access authentication, accessauthorization including checking of roaming rights, mobility managementcontrol (subscription and policies), network slicing support, and/orsession management function (SMF) selection. NAS may refer to thefunctionality operating between a CN and a UE, and AS may refer to thefunctionality operating between the UE and a RAN.

The 5G-CN 152 may include one or more additional network functions thatare not shown in FIG. 1B for the sake of clarity. For example, the 5G-CN152 may include one or more of a Session Management Function (SMF), anNR Repository Function (NRF), a Policy Control Function (PCF), a NetworkExposure Function (NEF), a Unified Data Management (UDM), an ApplicationFunction (AF), and/or an Authentication Server Function (AUSF).

The NG-RAN 154 may connect the 5G-CN 152 to the UEs 156 through radiocommunications over the air interface. The NG-RAN 154 may include one ormore gNBs, illustrated as gNB 160A and gNB 160B (collectively gNBs 160)and/or one or more ng-eNBs, illustrated as ng-eNB 162A and ng-eNB 162B(collectively ng-eNBs 162). The gNBs 160 and ng-eNBs 162 may be moregenerically referred to as base stations. The gNBs 160 and ng-eNBs 162may include one or more sets of antennas for communicating with the UEs156 over an air interface. For example, one or more of the gNBs 160and/or one or more of the ng-eNB s 162 may include three sets ofantennas to respectively control three cells (or sectors). Together, thecells of the gNBs 160 and the ng-eNBs 162 may provide radio coverage tothe UEs 156 over a wide geographic area to support UE mobility.

As shown in FIG. 1B, the gNBs 160 and/or the ng-eNBs 162 may beconnected to the 5G-CN 152 by means of an NG interface and to other basestations by an Xn interface. The NG and Xn interfaces may be establishedusing direct physical connections and/or indirect connections over anunderlying transport network, such as an internet protocol (IP)transport network. The gNBs 160 and/or the ng-eNBs 162 may be connectedto the UEs 156 by means of a Uu interface. For example, as illustratedin FIG. 1B, gNB 160A may be connected to the UE 156A by means of a Uuinterface. The NG, Xn, and Uu interfaces are associated with a protocolstack. The protocol stacks associated with the interfaces may be used bythe network elements in FIG. 1B to exchange data and signaling messagesand may include two planes: a user plane and a control plane. The userplane may handle data of interest to a user. The control plane mayhandle signaling messages of interest to the network elements.

The gNBs 160 and/or the ng-eNBs 162 may be connected to one or moreAMF/UPF functions of the 5G-CN 152, such as the AMF/UPF 158, by means ofone or more NG interfaces. For example, the gNB 160A may be connected tothe UPF 158B of the AMF/UPF 158 by means of an NG-User plane (NG-U)interface. The NG-U interface may provide delivery (e.g., non-guaranteeddelivery) of user plane PDUs between the gNB 160A and the UPF 158B. ThegNB 160A may be connected to the AMF 158A by means of an NG-Controlplane (NG-C) interface. The NG-C interface may provide, for example, NGinterface management, UE context management, UE mobility management,transport of NAS messages, paging, PDU session management, andconfiguration transfer and/or warning message transmission.

The gNBs 160 may provide NR user plane and control plane protocolterminations towards the UEs 156 over the Uu interface. For example, thegNB 160A may provide NR user plane and control plane protocolterminations toward the UE 156A over a Uu interface associated with afirst protocol stack. The ng-eNBs 162 may provide Evolved UMTSTerrestrial Radio Access (E-UTRA) user plane and control plane protocolterminations towards the UEs 156 over a Uu interface, where E-UTRArefers to the 3GPP 4G radio-access technology. For example, the ng-eNB162B may provide E-UTRA user plane and control plane protocolterminations towards the UE 156B over a Uu interface associated with asecond protocol stack.

The 5G-CN 152 was described as being configured to handle NR and 4Gradio accesses. It will be appreciated by one of ordinary skill in theart that it may be possible for NR to connect to a 4G core network in amode known as “non-standalone operation.” In non-standalone operation, a4G core network is used to provide (or at least support) control-planefunctionality (e.g., initial access, mobility, and paging). Althoughonly one AMF/UPF 158 is shown in FIG. 1B, one gNB or ng-eNB may beconnected to multiple AMF/UPF nodes to provide redundancy and/or to loadshare across the multiple AMF/UPF nodes.

As discussed, an interface (e.g., Uu, Xn, and NG interfaces) between thenetwork elements in FIG. 1B may be associated with a protocol stack thatthe network elements use to exchange data and signaling messages. Aprotocol stack may include two planes: a user plane and a control plane.The user plane may handle data of interest to a user, and the controlplane may handle signaling messages of interest to the network elements.

FIG. 2A and FIG. 2B respectively illustrate examples of NR user planeand NR control plane protocol stacks for the Uu interface that liesbetween a UE 210 and a gNB 220. The protocol stacks illustrated in FIG.2A and FIG. 2B may be the same or similar to those used for the Uuinterface between, for example, the UE 156A and the gNB 160A shown inFIG. 1B.

FIG. 2A illustrates a NR user plane protocol stack comprising fivelayers implemented in the UE 210 and the gNB 220. At the bottom of theprotocol stack, physical layers (PHYs) 211 and 221 may provide transportservices to the higher layers of the protocol stack and may correspondto layer 1 of the Open Systems Interconnection (OSI) model. The nextfour protocols above PHYs 211 and 221 comprise media access controllayers (MACs) 212 and 222, radio link control layers (RLCs) 213 and 223,packet data convergence protocol layers (PDCPs) 214 and 224, and servicedata application protocol layers (SDAPs) 215 and 225. Together, thesefour protocols may make up layer 2, or the data link layer, of the OSImodel.

FIG. 3 illustrates an example of services provided between protocollayers of the NR user plane protocol stack. Starting from the top ofFIG. 2A and FIG. 3, the SDAPs 215 and 225 may perform QoS flow handling.The UE 210 may receive services through a PDU session, which may be alogical connection between the UE 210 and a DN. The PDU session may haveone or more QoS flows. A UPF of a CN (e.g., the UPF 158B) may map IPpackets to the one or more QoS flows of the PDU session based on QoSrequirements (e.g., in terms of delay, data rate, and/or error rate).The SDAPs 215 and 225 may perform mapping/de-mapping between the one ormore QoS flows and one or more data radio bearers. Themapping/de-mapping between the QoS flows and the data radio bearers maybe determined by the SDAP 225 at the gNB 220. The SDAP 215 at the UE 210may be informed of the mapping between the QoS flows and the data radiobearers through reflective mapping or control signaling received fromthe gNB 220. For reflective mapping, the SDAP 225 at the gNB 220 maymark the downlink packets with a QoS flow indicator (QFI), which may beobserved by the SDAP 215 at the UE 210 to determine themapping/de-mapping between the QoS flows and the data radio bearers.

The PDCPs 214 and 224 may perform header compression/decompression toreduce the amount of data that needs to be transmitted over the airinterface, ciphering/deciphering to prevent unauthorized decoding ofdata transmitted over the air interface, and integrity protection (toensure control messages originate from intended sources. The PDCPs 214and 224 may perform retransmissions of undelivered packets, in-sequencedelivery and reordering of packets, and removal of packets received induplicate due to, for example, an intra-gNB handover. The PDCPs 214 and224 may perform packet duplication to improve the likelihood of thepacket being received and, at the receiver, remove any duplicatepackets. Packet duplication may be useful for services that require highreliability.

Although not shown in FIG. 3, PDCPs 214 and 224 may performmapping/de-mapping between a split radio bearer and RLC channels in adual connectivity scenario. Dual connectivity is a technique that allowsa UE to connect to two cells or, more generally, two cell groups: amaster cell group (MCG) and a secondary cell group (SCG). A split beareris when a single radio bearer, such as one of the radio bearers providedby the PDCPs 214 and 224 as a service to the SDAPs 215 and 225, ishandled by cell groups in dual connectivity. The PDCPs 214 and 224 maymap/de-map the split radio bearer between RLC channels belonging to cellgroups.

The RLCs 213 and 223 may perform segmentation, retransmission throughAutomatic Repeat Request (ARQ), and removal of duplicate data unitsreceived from MACs 212 and 222, respectively. The RLCs 213 and 223 maysupport three transmission modes: transparent mode (TM); unacknowledgedmode (UM); and acknowledged mode (AM). Based on the transmission mode anRLC is operating, the RLC may perform one or more of the notedfunctions. The RLC configuration may be per logical channel with nodependency on numerologies and/or Transmission Time Interval (TTI)durations. As shown in FIG. 3, the RLCs 213 and 223 may provide RLCchannels as a service to PDCPs 214 and 224, respectively.

The MACs 212 and 222 may perform multiplexing/demultiplexing of logicalchannels and/or mapping between logical channels and transport channels.The multiplexing/demultiplexing may include multiplexing/demultiplexingof data units, belonging to the one or more logical channels, into/fromTransport Blocks (TBs) delivered to/from the PHYs 211 and 221. The MAC222 may be configured to perform scheduling, scheduling informationreporting, and priority handling between UEs by means of dynamicscheduling. Scheduling may be performed in the gNB 220 (at the MAC 222)for downlink and uplink. The MACs 212 and 222 may be configured toperform error correction through Hybrid Automatic Repeat Request (HARQ)(e.g., one HARQ entity per carrier in case of Carrier Aggregation (CA)),priority handling between logical channels of the UE 210 by means oflogical channel prioritization, and/or padding. The MACs 212 and 222 maysupport one or more numerologies and/or transmission timings. In anexample, mapping restrictions in a logical channel prioritization maycontrol which numerology and/or transmission timing a logical channelmay use. As shown in FIG. 3, the MACs 212 and 222 may provide logicalchannels as a service to the RLCs 213 and 223.

The PHYs 211 and 221 may perform mapping of transport channels tophysical channels and digital and analog signal processing functions forsending and receiving information over the air interface. These digitaland analog signal processing functions may include, for example,coding/decoding and modulation/demodulation. The PHYs 211 and 221 mayperform multi-antenna mapping. As shown in FIG. 3, the PHYs 211 and 221may provide one or more transport channels as a service to the MACs 212and 222.

FIG. 4A illustrates an example downlink data flow through the NR userplane protocol stack. FIG. 4A illustrates a downlink data flow of threeIP packets (n, n+1, and m) through the NR user plane protocol stack togenerate two TBs at the gNB 220. An uplink data flow through the NR userplane protocol stack may be similar to the downlink data flow depictedin FIG. 4A.

The downlink data flow of FIG. 4A begins when SDAP 225 receives thethree IP packets from one or more QoS flows and maps the three packetsto radio bearers. In FIG. 4A, the SDAP 225 maps IP packets n and n+1 toa first radio bearer 402 and maps IP packet m to a second radio bearer404. An SDAP header (labeled with an “H” in FIG. 4A) is added to an IPpacket. The data unit from/to a higher protocol layer is referred to asa service data unit (SDU) of the lower protocol layer and the data unitto/from a lower protocol layer is referred to as a protocol data unit(PDU) of the higher protocol layer. As shown in FIG. 4A, the data unitfrom the SDAP 225 is an SDU of lower protocol layer PDCP 224 and is aPDU of the SDAP 225.

The remaining protocol layers in FIG. 4A may perform their associatedfunctionality (e.g., with respect to FIG. 3), add corresponding headers,and forward their respective outputs to the next lower layer. Forexample, the PDCP 224 may perform IP-header compression and cipheringand forward its output to the RLC 223. The RLC 223 may optionallyperform segmentation (e.g., as shown for IP packet m in FIG. 4A) andforward its output to the MAC 222. The MAC 222 may multiplex a number ofRLC PDUs and may attach a MAC subheader to an RLC PDU to form atransport block. In NR, the MAC subheaders may be distributed across theMAC PDU, as illustrated in FIG. 4A. In LTE, the MAC subheaders may beentirely located at the beginning of the MAC PDU. The NR MAC PDUstructure may reduce processing time and associated latency because theMAC PDU subheaders may be computed before the full MAC PDU is assembled.

FIG. 4B illustrates an example format of a MAC subheader in a MAC PDU.The MAC subheader includes: an SDU length field for indicating thelength (e.g., in bytes) of the MAC SDU to which the MAC subheadercorresponds; a logical channel identifier (LCID) field for identifyingthe logical channel from which the MAC SDU originated to aid in thedemultiplexing process; a flag (F) for indicating the size of the SDUlength field; and a reserved bit (R) field for future use.

FIG. 4B further illustrates MAC control elements (CEs) inserted into theMAC PDU by a MAC, such as MAC 223 or MAC 222. For example, FIG. 4Billustrates two MAC CEs inserted into the MAC PDU. MAC CEs may beinserted at the beginning of a MAC PDU for downlink transmissions (asshown in FIG. 4B) and at the end of a MAC PDU for uplink transmissions.MAC CEs may be used for in-band control signaling. Example MAC CEsinclude: scheduling-related MAC CEs, such as buffer status reports andpower headroom reports; activation/deactivation MAC CEs, such as thosefor activation/deactivation of PDCP duplication detection, channel stateinformation (CSI) reporting, sounding reference signal (SRS)transmission, and prior configured components; discontinuous reception(DRX) related MAC CEs; timing advance MAC CEs; and random access relatedMAC CEs. A MAC CE may be preceded by a MAC subheader with a similarformat as described for MAC SDUs and may be identified with a reservedvalue in the LCID field that indicates the type of control informationincluded in the MAC CE.

Before describing the NR control plane protocol stack, logical channels,transport channels, and physical channels are first described as well asa mapping between the channel types. One or more of the channels may beused to carry out functions associated with the NR control planeprotocol stack described later below.

FIG. 5A and FIG. 5B illustrate, for downlink and uplink respectively, amapping between logical channels, transport channels, and physicalchannels. Information is passed through channels between the RLC, theMAC, and the PHY of the NR protocol stack. A logical channel may be usedbetween the RLC and the MAC and may be classified as a control channelthat carries control and configuration information in the NR controlplane or as a traffic channel that carries data in the NR user plane. Alogical channel may be classified as a dedicated logical channel that isdedicated to a specific UE or as a common logical channel that may beused by more than one UE. A logical channel may also be defined by thetype of information it carries. The set of logical channels defined byNR include, for example:

-   -   a paging control channel (PCCH) for carrying paging messages        used to page a UE whose location is not known to the network on        a cell level;    -   a broadcast control channel (BCCH) for carrying system        information messages in the form of a master information block        (MIB) and several system information blocks (SIBs), wherein the        system information messages may be used by the UEs to obtain        information about how a cell is configured and how to operate        within the cell;    -   a common control channel (CCCH) for carrying control messages        together with random access;    -   a dedicated control channel (DCCH) for carrying control messages        to/from a specific the UE to configure the UE; and    -   a dedicated traffic channel (DTCH) for carrying user data        to/from a specific the UE.

Transport channels are used between the MAC and PHY layers and may bedefined by how the information they carry is transmitted over the airinterface. The set of transport channels defined by NR include, forexample:

-   -   a paging channel (PCH) for carrying paging messages that        originated from the PCCH;    -   a broadcast channel (BCH) for carrying the MIB from the BCCH;    -   a downlink shared channel (DL-SCH) for carrying downlink data        and signaling messages, including the SIBs from the BCCH;    -   an uplink shared channel (UL-SCH) for carrying uplink data and        signaling messages; and    -   a random access channel (RACH) for allowing a UE to contact the        network without any prior scheduling.

The PHY may use physical channels to pass information between processinglevels of the PHY. A physical channel may have an associated set oftime-frequency resources for carrying the information of one or moretransport channels. The PHY may generate control information to supportthe low-level operation of the PHY and provide the control informationto the lower levels of the PHY via physical control channels, known asL1/L2 control channels. The set of physical channels and physicalcontrol channels defined by NR include, for example:

-   -   a physical broadcast channel (PBCH) for carrying the MIB from        the BCH;    -   a physical downlink shared channel (PDSCH) for carrying downlink        data and signaling messages from the DL-SCH, as well as paging        messages from the PCH;    -   a physical downlink control channel (PDCCH) for carrying        downlink control information (DCI), which may include downlink        scheduling commands, uplink scheduling grants, and uplink power        control commands;    -   a physical uplink shared channel (PUSCH) for carrying uplink        data and signaling messages from the UL-SCH and in some        instances uplink control information (UCI) as described below;    -   a physical uplink control channel (PUCCH) for carrying UCI,        which may include HARQ acknowledgments, channel quality        indicators (CQI), pre-coding matrix indicators (PMI), rank        indicators (RI), and scheduling requests (SR); and    -   a physical random access channel (PRACH) for random access.

Similar to the physical control channels, the physical layer generatesphysical signals to support the low-level operation of the physicallayer. As shown in FIG. 5A and FIG. 5B, the physical layer signalsdefined by NR include: primary synchronization signals (PSS), secondarysynchronization signals (SSS), channel state information referencesignals (CSI-RS), demodulation reference signals (DMRS), soundingreference signals (SRS), and phase-tracking reference signals (PT-RS).These physical layer signals will be described in greater detail below.

FIG. 2B illustrates an example NR control plane protocol stack. As shownin FIG. 2B, the NR control plane protocol stack may use the same/similarfirst four protocol layers as the example NR user plane protocol stack.These four protocol layers include the PHYs 211 and 221, the MACs 212and 222, the RLCs 213 and 223, and the PDCPs 214 and 224. Instead ofhaving the SDAPs 215 and 225 at the top of the stack as in the NR userplane protocol stack, the NR control plane stack has radio resourcecontrols (RRCs) 216 and 226 and NAS protocols 217 and 237 at the top ofthe NR control plane protocol stack.

The NAS protocols 217 and 237 may provide control plane functionalitybetween the UE 210 and the AMF 230 (e.g., the AMF 158A) or, moregenerally, between the UE 210 and the CN. The NAS protocols 217 and 237may provide control plane functionality between the UE 210 and the AMF230 via signaling messages, referred to as NAS messages. There is nodirect path between the UE 210 and the AMF 230 through which the NASmessages can be transported. The NAS messages may be transported usingthe AS of the Uu and NG interfaces. NAS protocols 217 and 237 mayprovide control plane functionality such as authentication, security,connection setup, mobility management, and session management.

The RRCs 216 and 226 may provide control plane functionality between theUE 210 and the gNB 220 or, more generally, between the UE 210 and theRAN. The RRCs 216 and 226 may provide control plane functionalitybetween the UE 210 and the gNB 220 via signaling messages, referred toas RRC messages. RRC messages may be transmitted between the UE 210 andthe RAN using signaling radio bearers and the same/similar PDCP, RLC,MAC, and PHY protocol layers. The MAC may multiplex control-plane anduser-plane data into the same transport block (TB). The RRCs 216 and 226may provide control plane functionality such as: broadcast of systeminformation related to AS and NAS; paging initiated by the CN or theRAN; establishment, maintenance and release of an RRC connection betweenthe UE 210 and the RAN; security functions including key management;establishment, configuration, maintenance and release of signaling radiobearers and data radio bearers; mobility functions; QoS managementfunctions; the UE measurement reporting and control of the reporting;detection of and recovery from radio link failure (RLF); and/or NASmessage transfer. As part of establishing an RRC connection, RRCs 216and 226 may establish an RRC context, which may involve configuringparameters for communication between the UE 210 and the RAN.

FIG. 6 is an example diagram showing RRC state transitions of a UE. TheUE may be the same or similar to the wireless device 106 depicted inFIG. 1A, the UE 210 depicted in FIG. 2A and FIG. 2B, or any otherwireless device described in the present disclosure. As illustrated inFIG. 6, a UE may be in at least one of three RRC states: RRC connected602 (e.g., RRC_CONNECTED), RRC idle 604 (e.g., RRC_IDLE), and RRCinactive 606 (e.g., RRC_INACTIVE).

In RRC connected 602, the UE has an established RRC context and may haveat least one RRC connection with a base station. The base station may besimilar to one of the one or more base stations included in the RAN 104depicted in FIG. 1A, one of the gNBs 160 or ng-eNBs 162 depicted in FIG.1B, the gNB 220 depicted in FIG. 2A and FIG. 2B, or any other basestation described in the present disclosure. The base station with whichthe UE is connected may have the RRC context for the UE. The RRCcontext, referred to as the UE context, may comprise parameters forcommunication between the UE and the base station. These parameters mayinclude, for example: one or more AS contexts; one or more radio linkconfiguration parameters; bearer configuration information (e.g.,relating to a data radio bearer, signaling radio bearer, logicalchannel, QoS flow, and/or PDU session); security information; and/orPHY, MAC, RLC, PDCP, and/or SDAP layer configuration information. Whilein RRC connected 602, mobility of the UE may be managed by the RAN(e.g., the RAN 104 or the NG-RAN 154). The UE may measure the signallevels (e.g., reference signal levels) from a serving cell andneighboring cells and report these measurements to the base stationcurrently serving the UE. The UE's serving base station may request ahandover to a cell of one of the neighboring base stations based on thereported measurements. The RRC state may transition from RRC connected602 to RRC idle 604 through a connection release procedure 608 or to RRCinactive 606 through a connection inactivation procedure 610.

In RRC idle 604, an RRC context may not be established for the UE. InRRC idle 604, the UE may not have an RRC connection with the basestation. While in RRC idle 604, the UE may be in a sleep state for themajority of the time (e.g., to conserve battery power). The UE may wakeup periodically (e.g., once in every discontinuous reception cycle) tomonitor for paging messages from the RAN. Mobility of the UE may bemanaged by the UE through a procedure known as cell reselection. The RRCstate may transition from RRC idle 604 to RRC connected 602 through aconnection establishment procedure 612, which may involve a randomaccess procedure as discussed in greater detail below.

In RRC inactive 606, the RRC context previously established ismaintained in the UE and the base station. This allows for a fasttransition to RRC connected 602 with reduced signaling overhead ascompared to the transition from RRC idle 604 to RRC connected 602. Whilein RRC inactive 606, the UE may be in a sleep state and mobility of theUE may be managed by the UE through cell reselection. The RRC state maytransition from RRC inactive 606 to RRC connected 602 through aconnection resume procedure 614 or to RRC idle 604 though a connectionrelease procedure 616 that may be the same as or similar to connectionrelease procedure 608.

An RRC state may be associated with a mobility management mechanism. InRRC idle 604 and RRC inactive 606, mobility is managed by the UE throughcell reselection. The purpose of mobility management in RRC idle 604 andRRC inactive 606 is to allow the network to be able to notify the UE ofan event via a paging message without having to broadcast the pagingmessage over the entire mobile communications network. The mobilitymanagement mechanism used in RRC idle 604 and RRC inactive 606 may allowthe network to track the UE on a cell-group level so that the pagingmessage may be broadcast over the cells of the cell group that the UEcurrently resides within instead of the entire mobile communicationnetwork. The mobility management mechanisms for RRC idle 604 and RRCinactive 606 track the UE on a cell-group level. They may do so usingdifferent granularities of grouping. For example, there may be threelevels of cell-grouping granularity: individual cells; cells within aRAN area identified by a RAN area identifier (RAI); and cells within agroup of RAN areas, referred to as a tracking area and identified by atracking area identifier (TAI).

Tracking areas may be used to track the UE at the CN level. The CN(e.g., the CN 102 or the 5G-CN 152) may provide the UE with a list ofTAIs associated with a UE registration area. If the UE moves, throughcell reselection, to a cell associated with a TAI not included in thelist of TAIs associated with the UE registration area, the UE mayperform a registration update with the CN to allow the CN to update theUE's location and provide the UE with a new the UE registration area.

RAN areas may be used to track the UE at the RAN level. For a UE in RRCinactive 606 state, the UE may be assigned a RAN notification area. ARAN notification area may comprise one or more cell identities, a listof RAIs, or a list of TAIs. In an example, a base station may belong toone or more RAN notification areas. In an example, a cell may belong toone or more RAN notification areas. If the UE moves, through cellreselection, to a cell not included in the RAN notification areaassigned to the UE, the UE may perform a notification area update withthe RAN to update the UE's RAN notification area.

A base station storing an RRC context for a UE or a last serving basestation of the UE may be referred to as an anchor base station. Ananchor base station may maintain an RRC context for the UE at leastduring a period of time that the UE stays in a RAN notification area ofthe anchor base station and/or during a period of time that the UE staysin RRC inactive 606.

A gNB, such as gNBs 160 in FIG. 1B, may be split in two parts: a centralunit (gNB-CU), and one or more distributed units (gNB-DU). A gNB-CU maybe coupled to one or more gNB-DUs using an F1 interface. The gNB-CU maycomprise the RRC, the PDCP, and the SDAP. A gNB-DU may comprise the RLC,the MAC, and the PHY.

In NR, the physical signals and physical channels (discussed withrespect to FIG. 5A and FIG. 5B) may be mapped onto orthogonal frequencydivisional multiplexing (OFDM) symbols. OFDM is a multicarriercommunication scheme that transmits data over F orthogonal subcarriers(or tones). Before transmission, the data may be mapped to a series ofcomplex symbols (e.g., M-quadrature amplitude modulation (M-QAM) orM-phase shift keying (M-PSK) symbols), referred to as source symbols,and divided into F parallel symbol streams. The F parallel symbolstreams may be treated as though they are in the frequency domain andused as inputs to an Inverse Fast Fourier Transform (IFFT) block thattransforms them into the time domain. The IFFT block may take in Fsource symbols at a time, one from each of the F parallel symbolstreams, and use each source symbol to modulate the amplitude and phaseof one of F sinusoidal basis functions that correspond to the Forthogonal subcarriers. The output of the IFFT block may be Ftime-domain samples that represent the summation of the F orthogonalsubcarriers. The F time-domain samples may form a single OFDM symbol.After some processing (e.g., addition of a cyclic prefix) andup-conversion, an OFDM symbol provided by the IFFT block may betransmitted over the air interface on a carrier frequency. The Fparallel symbol streams may be mixed using an FFT block before beingprocessed by the IFFT block. This operation produces Discrete FourierTransform (DFT)-precoded OFDM symbols and may be used by UEs in theuplink to reduce the peak to average power ratio (PAPR). Inverseprocessing may be performed on the OFDM symbol at a receiver using anFFT block to recover the data mapped to the source symbols.

FIG. 7 illustrates an example configuration of an NR frame into whichOFDM symbols are grouped. An NR frame may be identified by a systemframe number (SFN). The SFN may repeat with a period of 1024 frames. Asillustrated, one NR frame may be 10 milliseconds (ms) in duration andmay include 10 subframes that are 1 ms in duration. A subframe may bedivided into slots that include, for example, 14 OFDM symbols per slot.

The duration of a slot may depend on the numerology used for the OFDMsymbols of the slot. In NR, a flexible numerology is supported toaccommodate different cell deployments (e.g., cells with carrierfrequencies below 1 GHz up to cells with carrier frequencies in themm-wave range). A numerology may be defined in terms of subcarrierspacing and cyclic prefix duration. For a numerology in NR, subcarrierspacings may be scaled up by powers of two from a baseline subcarrierspacing of 15 kHz, and cyclic prefix durations may be scaled down bypowers of two from a baseline cyclic prefix duration of 4.7 μs. Forexample, NR defines numerologies with the following subcarrierspacing/cyclic prefix duration combinations: 15 kHz/4.7 μs; 30 kHz/2.3μs; 60 kHz/1.2 μs; 120 kHz/0.59 μs; and 240 kHz/0.29 μs.

A slot may have a fixed number of OFDM symbols (e.g., 14 OFDM symbols).A numerology with a higher subcarrier spacing has a shorter slotduration and, correspondingly, more slots per subframe. FIG. 7illustrates this numerology-dependent slot duration andslots-per-subframe transmission structure (the numerology with asubcarrier spacing of 240 kHz is not shown in FIG. 7 for ease ofillustration). A subframe in NR may be used as a numerology-independenttime reference, while a slot may be used as the unit upon which uplinkand downlink transmissions are scheduled. To support low latency,scheduling in NR may be decoupled from the slot duration and start atany OFDM symbol and last for as many symbols as needed for atransmission. These partial slot transmissions may be referred to asmini-slot or subslot transmissions.

FIG. 8 illustrates an example configuration of a slot in the time andfrequency domain for an NR carrier. The slot includes resource elements(REs) and resource blocks (RBs). An RE is the smallest physical resourcein NR. An RE spans one OFDM symbol in the time domain by one subcarrierin the frequency domain as shown in FIG. 8. An RB spans twelveconsecutive REs in the frequency domain as shown in FIG. 8. An NRcarrier may be limited to a width of 275 RBs or 275×12=3300 subcarriers.Such a limitation, if used, may limit the NR carrier to 50, 100, 200,and 400 MHz for subcarrier spacings of 15, 30, 60, and 120 kHz,respectively, where the 400 MHz bandwidth may be set based on a 400 MHzper carrier bandwidth limit.

FIG. 8 illustrates a single numerology being used across the entirebandwidth of the NR carrier. In other example configurations, multiplenumerologies may be supported on the same carrier.

NR may support wide carrier bandwidths (e.g., up to 400 MHz for asubcarrier spacing of 120 kHz). Not all UEs may be able to receive thefull carrier bandwidth (e.g., due to hardware limitations). Also,receiving the full carrier bandwidth may be prohibitive in terms of UEpower consumption. In an example, to reduce power consumption and/or forother purposes, a UE may adapt the size of the UE's receive bandwidthbased on the amount of traffic the UE is scheduled to receive. This isreferred to as bandwidth adaptation.

NR defines bandwidth parts (BWPs) to support UEs not capable ofreceiving the full carrier bandwidth and to support bandwidthadaptation. In an example, a BWP may be defined by a subset ofcontiguous RBs on a carrier. A UE may be configured (e.g., via RRClayer) with one or more downlink BWPs and one or more uplink BWPs perserving cell (e.g., up to four downlink BWPs and up to four uplink BWPsper serving cell). At a given time, one or more of the configured BWPsfor a serving cell may be active. These one or more BWPs may be referredto as active BWPs of the serving cell. When a serving cell is configuredwith a secondary uplink carrier, the serving cell may have one or morefirst active BWPs in the uplink carrier and one or more second activeBWPs in the secondary uplink carrier.

For unpaired spectra, a downlink BWP from a set of configured downlinkBWPs may be linked with an uplink BWP from a set of configured uplinkBWPs if a downlink BWP index of the downlink BWP and an uplink BWP indexof the uplink BWP are the same. For unpaired spectra, a UE may expectthat a center frequency for a downlink BWP is the same as a centerfrequency for an uplink BWP.

For a downlink BWP in a set of configured downlink BWPs on a primarycell (PCell), a base station may configure a UE with one or more controlresource sets (CORESETs) for at least one search space. A search spaceis a set of locations in the time and frequency domains where the UE mayfind control information. The search space may be a UE-specific searchspace or a common search space (potentially usable by a plurality ofUEs). For example, a base station may configure a UE with a commonsearch space, on a PCell or on a primary secondary cell (PSCell), in anactive downlink BWP.

For an uplink BWP in a set of configured uplink BWPs, a BS may configurea UE with one or more resource sets for one or more PUCCH transmissions.A UE may receive downlink receptions (e.g., PDCCH or PDSCH) in adownlink BWP according to a configured numerology (e.g., subcarrierspacing and cyclic prefix duration) for the downlink BWP. The UE maytransmit uplink transmissions (e.g., PUCCH or PUSCH) in an uplink BWPaccording to a configured numerology (e.g., subcarrier spacing andcyclic prefix length for the uplink BWP).

One or more BWP indicator fields may be provided in Downlink ControlInformation (DCI). A value of a BWP indicator field may indicate whichBWP in a set of configured BWPs is an active downlink BWP for one ormore downlink receptions. The value of the one or more BWP indicatorfields may indicate an active uplink BWP for one or more uplinktransmissions.

A base station may semi-statically configure a UE with a defaultdownlink BWP within a set of configured downlink BWPs associated with aPCell. If the base station does not provide the default downlink BWP tothe UE, the default downlink BWP may be an initial active downlink BWP.The UE may determine which BWP is the initial active downlink BWP basedon a CORESET configuration obtained using the PBCH.

A base station may configure a UE with a BWP inactivity timer value fora PCell. The UE may start or restart a BWP inactivity timer at anyappropriate time. For example, the UE may start or restart the BWPinactivity timer (a) when the UE detects a DCI indicating an activedownlink BWP other than a default downlink BWP for a paired spectraoperation; or (b) when a UE detects a DCI indicating an active downlinkBWP or active uplink BWP other than a default downlink BWP or uplink BWPfor an unpaired spectra operation. If the UE does not detect DCI duringan interval of time (e.g., 1 ms or 0.5 ms), the UE may run the BWPinactivity timer toward expiration (for example, increment from zero tothe BWP inactivity timer value, or decrement from the BWP inactivitytimer value to zero). When the BWP inactivity timer expires, the UE mayswitch from the active downlink BWP to the default downlink BWP.

In an example, a base station may semi-statically configure a UE withone or more BWPs. A UE may switch an active BWP from a first BWP to asecond BWP in response to receiving a DCI indicating the second BWP asan active BWP and/or in response to an expiry of the BWP inactivitytimer (e.g., if the second BWP is the default BWP).

Downlink and uplink BWP switching (where BWP switching refers toswitching from a currently active BWP to a not currently active BWP) maybe performed independently in paired spectra. In unpaired spectra,downlink and uplink BWP switching may be performed simultaneously.Switching between configured BWPs may occur based on RRC signaling, DCI,expiration of a BWP inactivity timer, and/or an initiation of randomaccess.

FIG. 9 illustrates an example of bandwidth adaptation using threeconfigured BWPs for an NR carrier. A UE configured with the three BWPsmay switch from one BWP to another BWP at a switching point. In theexample illustrated in FIG. 9, the BWPs include: a BWP 902 with abandwidth of 40 MHz and a subcarrier spacing of 15 kHz; a BWP 904 with abandwidth of 10 MHz and a subcarrier spacing of 15 kHz; and a BWP 906with a bandwidth of 20 MHz and a subcarrier spacing of 60 kHz. The BWP902 may be an initial active BWP, and the BWP 904 may be a default BWP.The UE may switch between BWPs at switching points. In the example ofFIG. 9, the UE may switch from the BWP 902 to the BWP 904 at a switchingpoint 908. The switching at the switching point 908 may occur for anysuitable reason, for example, in response to an expiry of a BWPinactivity timer (indicating switching to the default BWP) and/or inresponse to receiving a DCI indicating BWP 904 as the active BWP. The UEmay switch at a switching point 910 from active BWP 904 to BWP 906 inresponse receiving a DCI indicating BWP 906 as the active BWP. The UEmay switch at a switching point 912 from active BWP 906 to BWP 904 inresponse to an expiry of a BWP inactivity timer and/or in responsereceiving a DCI indicating BWP 904 as the active BWP. The UE may switchat a switching point 914 from active BWP 904 to BWP 902 in responsereceiving a DCI indicating BWP 902 as the active BWP.

If a UE is configured for a secondary cell with a default downlink BWPin a set of configured downlink BWPs and a timer value, UE proceduresfor switching BWPs on a secondary cell may be the same/similar as thoseon a primary cell. For example, the UE may use the timer value and thedefault downlink BWP for the secondary cell in the same/similar manneras the UE would use these values for a primary cell.

To provide for greater data rates, two or more carriers can beaggregated and simultaneously transmitted to/from the same UE usingcarrier aggregation (CA). The aggregated carriers in CA may be referredto as component carriers (CCs). When CA is used, there are a number ofserving cells for the UE, one for a CC. The CCs may have threeconfigurations in the frequency domain.

FIG. 10A illustrates the three CA configurations with two CCs. In theintraband, contiguous configuration 1002, the two CCs are aggregated inthe same frequency band (frequency band A) and are located directlyadjacent to each other within the frequency band. In the intraband,non-contiguous configuration 1004, the two CCs are aggregated in thesame frequency band (frequency band A) and are separated in thefrequency band by a gap. In the interband configuration 1006, the twoCCs are located in frequency bands (frequency band A and frequency bandB).

In an example, up to 32 CCs may be aggregated. The aggregated CCs mayhave the same or different bandwidths, subcarrier spacing, and/orduplexing schemes (TDD or FDD). A serving cell for a UE using CA mayhave a downlink CC. For FDD, one or more uplink CCs may be optionallyconfigured for a serving cell. The ability to aggregate more downlinkcarriers than uplink carriers may be useful, for example, when the UEhas more data traffic in the downlink than in the uplink.

When CA is used, one of the aggregated cells for a UE may be referred toas a primary cell (PCell). The PCell may be the serving cell that the UEinitially connects to at RRC connection establishment, reestablishment,and/or handover. The PCell may provide the UE with NAS mobilityinformation and the security input. UEs may have different PCells. Inthe downlink, the carrier corresponding to the PCell may be referred toas the downlink primary CC (DL PCC). In the uplink, the carriercorresponding to the PCell may be referred to as the uplink primary CC(UL PCC). The other aggregated cells for the UE may be referred to assecondary cells (SCells). In an example, the SCells may be configuredafter the PCell is configured for the UE. For example, an SCell may beconfigured through an RRC Connection Reconfiguration procedure. In thedownlink, the carrier corresponding to an SCell may be referred to as adownlink secondary CC (DL SCC). In the uplink, the carrier correspondingto the SCell may be referred to as the uplink secondary CC (UL SCC).

Configured SCells for a UE may be activated and deactivated based on,for example, traffic and channel conditions. Deactivation of an SCellmay mean that PDCCH and PDSCH reception on the SCell is stopped andPUSCH, SRS, and CQI transmissions on the SCell are stopped. ConfiguredSCells may be activated and deactivated using a MAC CE with respect toFIG. 4B. For example, a MAC CE may use a bitmap (e.g., one bit perSCell) to indicate which SCells (e.g., in a subset of configured SCells)for the UE are activated or deactivated. Configured SCells may bedeactivated in response to an expiration of an SCell deactivation timer(e.g., one SCell deactivation timer per SCell).

Downlink control information, such as scheduling assignments andscheduling grants, for a cell may be transmitted on the cellcorresponding to the assignments and grants, which is known asself-scheduling. The DCI for the cell may be transmitted on anothercell, which is known as cross-carrier scheduling. Uplink controlinformation (e.g., HARQ acknowledgments and channel state feedback, suchas CQI, PMI, and/or RI) for aggregated cells may be transmitted on thePUCCH of the PCell. For a larger number of aggregated downlink CCs, thePUCCH of the PCell may become overloaded. Cells may be divided intomultiple PUCCH groups.

FIG. 10B illustrates an example of how aggregated cells may beconfigured into one or more PUCCH groups. A PUCCH group 1010 and a PUCCHgroup 1050 may include one or more downlink CCs, respectively. In theexample of FIG. 10B, the PUCCH group 1010 includes three downlink CCs: aPCell 1011, an SCell 1012, and an SCell 1013. The PUCCH group 1050includes three downlink CCs in the present example: a PCell 1051, anSCell 1052, and an SCell 1053. One or more uplink CCs may be configuredas a PCell 1021, an SCell 1022, and an SCell 1023. One or more otheruplink CCs may be configured as a primary Scell (PSCell) 1061, an SCell1062, and an SCell 1063. Uplink control information (UCI) related to thedownlink CCs of the PUCCH group 1010, shown as UCI 1031, UCI 1032, andUCI 1033, may be transmitted in the uplink of the PCell 1021. Uplinkcontrol information (UCI) related to the downlink CCs of the PUCCH group1050, shown as UCI 1071, UCI 1072, and UCI 1073, may be transmitted inthe uplink of the PSCell 1061. In an example, if the aggregated cellsdepicted in FIG. 10B were not divided into the PUCCH group 1010 and thePUCCH group 1050, a single uplink PCell to transmit UCI relating to thedownlink CCs, and the PCell may become overloaded. By dividingtransmissions of UCI between the PCell 1021 and the PSCell 1061,overloading may be prevented.

A cell, comprising a downlink carrier and optionally an uplink carrier,may be assigned with a physical cell ID and a cell index. The physicalcell ID or the cell index may identify a downlink carrier and/or anuplink carrier of the cell, for example, depending on the context inwhich the physical cell ID is used. A physical cell ID may be determinedusing a synchronization signal transmitted on a downlink componentcarrier. A cell index may be determined using RRC messages. In thedisclosure, a physical cell ID may be referred to as a carrier ID, and acell index may be referred to as a carrier index. For example, when thedisclosure refers to a first physical cell ID for a first downlinkcarrier, the disclosure may mean the first physical cell ID is for acell comprising the first downlink carrier. The same/similar concept mayapply to, for example, a carrier activation. When the disclosureindicates that a first carrier is activated, the specification may meanthat a cell comprising the first carrier is activated.

In CA, a multi-carrier nature of a PHY may be exposed to a MAC. In anexample, a HARQ entity may operate on a serving cell. A transport blockmay be generated per assignment/grant per serving cell. A transportblock and potential HARQ retransmissions of the transport block may bemapped to a serving cell.

In the downlink, a base station may transmit (e.g., unicast, multicast,and/or broadcast) one or more Reference Signals (RSs) to a UE (e.g.,PSS, SSS, CSI-RS, DMRS, and/or PT-RS, as shown in FIG. 5A). In theuplink, the UE may transmit one or more RSs to the base station (e.g.,DMRS, PT-RS, and/or SRS, as shown in FIG. 5B). The PSS and the SSS maybe transmitted by the base station and used by the UE to synchronize theUE to the base station. The PSS and the SSS may be provided in asynchronization signal (SS)/physical broadcast channel (PBCH) block thatincludes the PSS, the SSS, and the PBCH. The base station mayperiodically transmit a burst of SS/PBCH blocks.

FIG. 11A illustrates an example of an SS/PBCH block's structure andlocation. A burst of SS/PBCH blocks may include one or more SS/PBCHblocks (e.g., 4 SS/PBCH blocks, as shown in FIG. 11A). Bursts may betransmitted periodically (e.g., every 2 frames or 20 ms). A burst may berestricted to a half-frame (e.g., a first half-frame having a durationof 5 ms). It will be understood that FIG. 11A is an example, and thatthese parameters (number of SS/PBCH blocks per burst, periodicity ofbursts, position of burst within the frame) may be configured based on,for example: a carrier frequency of a cell in which the SS/PBCH block istransmitted; a numerology or subcarrier spacing of the cell; aconfiguration by the network (e.g., using RRC signaling); or any othersuitable factor. In an example, the UE may assume a subcarrier spacingfor the SS/PBCH block based on the carrier frequency being monitored,unless the radio network configured the UE to assume a differentsubcarrier spacing.

The SS/PBCH block may span one or more OFDM symbols in the time domain(e.g., 4 OFDM symbols, as shown in the example of FIG. 11A) and may spanone or more subcarriers in the frequency domain (e.g., 240 contiguoussubcarriers). The PSS, the SSS, and the PBCH may have a common centerfrequency. The PSS may be transmitted first and may span, for example, 1OFDM symbol and 127 subcarriers. The SSS may be transmitted after thePSS (e.g., two symbols later) and may span 1 OFDM symbol and 127subcarriers. The PBCH may be transmitted after the PSS (e.g., across thenext 3 OFDM symbols) and may span 240 subcarriers.

The location of the SS/PBCH block in the time and frequency domains maynot be known to the UE (e.g., if the UE is searching for the cell). Tofind and select the cell, the UE may monitor a carrier for the PSS. Forexample, the UE may monitor a frequency location within the carrier. Ifthe PSS is not found after a certain duration (e.g., 20 ms), the UE maysearch for the PSS at a different frequency location within the carrier,as indicated by a synchronization raster. If the PSS is found at alocation in the time and frequency domains, the UE may determine, basedon a known structure of the SS/PBCH block, the locations of the SSS andthe PBCH, respectively. The SS/PBCH block may be a cell-defining SSblock (CD-SSB). In an example, a primary cell may be associated with aCD-SSB. The CD-SSB may be located on a synchronization raster. In anexample, a cell selection/search and/or reselection may be based on theCD-SSB.

The SS/PBCH block may be used by the UE to determine one or moreparameters of the cell. For example, the UE may determine a physicalcell identifier (PCI) of the cell based on the sequences of the PSS andthe SSS, respectively. The UE may determine a location of a frameboundary of the cell based on the location of the SS/PBCH block. Forexample, the SS/PBCH block may indicate that it has been transmitted inaccordance with a transmission pattern, wherein a SS/PBCH block in thetransmission pattern is a known distance from the frame boundary.

The PBCH may use a QPSK modulation and may use forward error correction(FEC). The FEC may use polar coding. One or more symbols spanned by thePBCH may carry one or more DMRSs for demodulation of the PBCH. The PBCHmay include an indication of a current system frame number (SFN) of thecell and/or a SS/PBCH block timing index. These parameters mayfacilitate time synchronization of the UE to the base station. The PBCHmay include a master information block (MIB) used to provide the UE withone or more parameters. The MIB may be used by the UE to locateremaining minimum system information (RMSI) associated with the cell.The RMSI may include a System Information Block Type 1 (SIB1). The SIB1may contain information needed by the UE to access the cell. The UE mayuse one or more parameters of the MIB to monitor PDCCH, which may beused to schedule PDSCH. The PDSCH may include the SIB1. The SIB1 may bedecoded using parameters provided in the MIB. The PBCH may indicate anabsence of SIB1. Based on the PBCH indicating the absence of SIB1, theUE may be pointed to a frequency. The UE may search for an SS/PBCH blockat the frequency to which the UE is pointed.

The UE may assume that one or more SS/PBCH blocks transmitted with asame SS/PBCH block index are quasi co-located (QCLed) (e.g., having thesame/similar Doppler spread, Doppler shift, average gain, average delay,and/or spatial Rx parameters). The UE may not assume QCL for SS/PBCHblock transmissions having different SS/PBCH block indices.

SS/PBCH blocks (e.g., those within a half-frame) may be transmitted inspatial directions (e.g., using different beams that span a coveragearea of the cell). In an example, a first SS/PBCH block may betransmitted in a first spatial direction using a first beam, and asecond SS/PBCH block may be transmitted in a second spatial directionusing a second beam.

In an example, within a frequency span of a carrier, a base station maytransmit a plurality of SS/PBCH blocks. In an example, a first PCI of afirst SS/PBCH block of the plurality of SS/PBCH blocks may be differentfrom a second PCI of a second SS/PBCH block of the plurality of SS/PBCHblocks. The PCIs of SS/PBCH blocks transmitted in different frequencylocations may be different or the same.

The CSI-RS may be transmitted by the base station and used by the UE toacquire channel state information (CSI). The base station may configurethe UE with one or more CSI-RSs for channel estimation or any othersuitable purpose. The base station may configure a UE with one or moreof the same/similar CSI-RSs. The UE may measure the one or more CSI-RSs.The UE may estimate a downlink channel state and/or generate a CSIreport based on the measuring of the one or more downlink CSI-RSs. TheUE may provide the CSI report to the base station. The base station mayuse feedback provided by the UE (e.g., the estimated downlink channelstate) to perform link adaptation.

The base station may semi-statically configure the UE with one or moreCSI-RS resource sets. A CSI-RS resource may be associated with alocation in the time and frequency domains and a periodicity. The basestation may selectively activate and/or deactivate a CSI-RS resource.The base station may indicate to the UE that a CSI-RS resource in theCSI-RS resource set is activated and/or deactivated.

The base station may configure the UE to report CSI measurements. Thebase station may configure the UE to provide CSI reports periodically,aperiodically, or semi-persistently. For periodic CSI reporting, the UEmay be configured with a timing and/or periodicity of a plurality of CSIreports. For aperiodic CSI reporting, the base station may request a CSIreport. For example, the base station may command the UE to measure aconfigured CSI-RS resource and provide a CSI report relating to themeasurements. For semi-persistent CSI reporting, the base station mayconfigure the UE to transmit periodically, and selectively activate ordeactivate the periodic reporting. The base station may configure the UEwith a CSI-RS resource set and CSI reports using RRC signaling.

The CSI-RS configuration may comprise one or more parameters indicating,for example, up to 32 antenna ports. The UE may be configured to employthe same OFDM symbols for a downlink CSI-RS and a control resource set(CORESET) when the downlink CSI-RS and CORESET are spatially QCLed andresource elements associated with the downlink CSI-RS are outside of thephysical resource blocks (PRBs) configured for the CORESET. The UE maybe configured to employ the same OFDM symbols for downlink CSI-RS andSS/PBCH blocks when the downlink CSI-RS and SS/PBCH blocks are spatiallyQCLed and resource elements associated with the downlink CSI-RS areoutside of PRBs configured for the SS/PBCH blocks.

Downlink DMRSs may be transmitted by a base station and used by a UE forchannel estimation. For example, the downlink DMRS may be used forcoherent demodulation of one or more downlink physical channels (e.g.,PDSCH). An NR network may support one or more variable and/orconfigurable DMRS patterns for data demodulation. At least one downlinkDMRS configuration may support a front-loaded DMRS pattern. Afront-loaded DMRS may be mapped over one or more OFDM symbols (e.g., oneor two adjacent OFDM symbols). A base station may semi-staticallyconfigure the UE with a number (e.g. a maximum number) of front-loadedDMRS symbols for PDSCH. A DMRS configuration may support one or moreDMRS ports. For example, for single user-MIMO, a DMRS configuration maysupport up to eight orthogonal downlink DMRS ports per UE. Formultiuser-MIMO, a DMRS configuration may support up to 4 orthogonaldownlink DMRS ports per UE. A radio network may support (e.g., at leastfor CP-OFDM) a common DMRS structure for downlink and uplink, wherein aDMRS location, a DMRS pattern, and/or a scrambling sequence may be thesame or different. The base station may transmit a downlink DMRS and acorresponding PDSCH using the same precoding matrix. The UE may use theone or more downlink DMRSs for coherent demodulation/channel estimationof the PDSCH.

In an example, a transmitter (e.g., a base station) may use a precodermatrices for a part of a transmission bandwidth. For example, thetransmitter may use a first precoder matrix for a first bandwidth and asecond precoder matrix for a second bandwidth. The first precoder matrixand the second precoder matrix may be different based on the firstbandwidth being different from the second bandwidth. The UE may assumethat a same precoding matrix is used across a set of PRBs. The set ofPRBs may be denoted as a precoding resource block group (PRG).

A PDSCH may comprise one or more layers. The UE may assume that at leastone symbol with DMRS is present on a layer of the one or more layers ofthe PDSCH. A higher layer may configure up to 3 DMRSs for the PDSCH.

Downlink PT-RS may be transmitted by a base station and used by a UE forphase-noise compensation. Whether a downlink PT-RS is present or not maydepend on an RRC configuration. The presence and/or pattern of thedownlink PT-RS may be configured on a UE-specific basis using acombination of RRC signaling and/or an association with one or moreparameters employed for other purposes (e.g., modulation and codingscheme (MCS)), which may be indicated by DCI. When configured, a dynamicpresence of a downlink PT-RS may be associated with one or more DCIparameters comprising at least MCS. An NR network may support aplurality of PT-RS densities defined in the time and/or frequencydomains. When present, a frequency domain density may be associated withat least one configuration of a scheduled bandwidth. The UE may assume asame precoding for a DMRS port and a PT-RS port. A number of PT-RS portsmay be fewer than a number of DMRS ports in a scheduled resource.Downlink PT-RS may be confined in the scheduled time/frequency durationfor the UE. Downlink PT-RS may be transmitted on symbols to facilitatephase tracking at the receiver.

The UE may transmit an uplink DMRS to a base station for channelestimation. For example, the base station may use the uplink DMRS forcoherent demodulation of one or more uplink physical channels. Forexample, the UE may transmit an uplink DMRS with a PUSCH and/or a PUCCH.The uplink DM-RS may span a range of frequencies that is similar to arange of frequencies associated with the corresponding physical channel.The base station may configure the UE with one or more uplink DMRSconfigurations. At least one DMRS configuration may support afront-loaded DMRS pattern. The front-loaded DMRS may be mapped over oneor more OFDM symbols (e.g., one or two adjacent OFDM symbols). One ormore uplink DMRSs may be configured to transmit at one or more symbolsof a PUSCH and/or a PUCCH. The base station may semi-staticallyconfigure the UE with a number (e.g. maximum number) of front-loadedDMRS symbols for the PUSCH and/or the PUCCH, which the UE may use toschedule a single-symbol DMRS and/or a double-symbol DMRS. An NR networkmay support (e.g., for cyclic prefix orthogonal frequency divisionmultiplexing (CP-OFDM)) a common DMRS structure for downlink and uplink,wherein a DMRS location, a DMRS pattern, and/or a scrambling sequencefor the DMRS may be the same or different.

A PUSCH may comprise one or more layers, and the UE may transmit atleast one symbol with DMRS present on a layer of the one or more layersof the PUSCH. In an example, a higher layer may configure up to threeDMRSs for the PUSCH.

Uplink PT-RS (which may be used by a base station for phase trackingand/or phase-noise compensation) may or may not be present depending onan RRC configuration of the UE. The presence and/or pattern of uplinkPT-RS may be configured on a UE-specific basis by a combination of RRCsignaling and/or one or more parameters employed for other purposes(e.g., Modulation and Coding Scheme (MCS)), which may be indicated byDCI. When configured, a dynamic presence of uplink PT-RS may beassociated with one or more DCI parameters comprising at least MCS. Aradio network may support a plurality of uplink PT-RS densities definedin time/frequency domain. When present, a frequency domain density maybe associated with at least one configuration of a scheduled bandwidth.The UE may assume a same precoding for a DMRS port and a PT-RS port. Anumber of PT-RS ports may be fewer than a number of DMRS ports in ascheduled resource. For example, uplink PT-RS may be confined in thescheduled time/frequency duration for the UE.

SRS may be transmitted by a UE to a base station for channel stateestimation to support uplink channel dependent scheduling and/or linkadaptation. SRS transmitted by the UE may allow a base station toestimate an uplink channel state at one or more frequencies. A schedulerat the base station may employ the estimated uplink channel state toassign one or more resource blocks for an uplink PUSCH transmission fromthe UE. The base station may semi-statically configure the UE with oneor more SRS resource sets. For an SRS resource set, the base station mayconfigure the UE with one or more SRS resources. An SRS resource setapplicability may be configured by a higher layer (e.g., RRC) parameter.For example, when a higher layer parameter indicates beam management, anSRS resource in a SRS resource set of the one or more SRS resource sets(e.g., with the same/similar time domain behavior, periodic, aperiodic,and/or the like) may be transmitted at a time instant (e.g.,simultaneously). The UE may transmit one or more SRS resources in SRSresource sets. An NR network may support aperiodic, periodic and/orsemi-persistent SRS transmissions. The UE may transmit SRS resourcesbased on one or more trigger types, wherein the one or more triggertypes may comprise higher layer signaling (e.g., RRC) and/or one or moreDCI formats. In an example, at least one DCI format may be employed forthe UE to select at least one of one or more configured SRS resourcesets. An SRS trigger type 0 may refer to an SRS triggered based on ahigher layer signaling. An SRS trigger type 1 may refer to an SRStriggered based on one or more DCI formats. In an example, when PUSCHand SRS are transmitted in a same slot, the UE may be configured totransmit SRS after a transmission of a PUSCH and a corresponding uplinkDMRS.

The base station may semi-statically configure the UE with one or moreSRS configuration parameters indicating at least one of following: a SRSresource configuration identifier; a number of SRS ports; time domainbehavior of an SRS resource configuration (e.g., an indication ofperiodic, semi-persistent, or aperiodic SRS); slot, mini-slot, and/orsubframe level periodicity; offset for a periodic and/or an aperiodicSRS resource; a number of OFDM symbols in an SRS resource; a startingOFDM symbol of an SRS resource; an SRS bandwidth; a frequency hoppingbandwidth; a cyclic shift; and/or an SRS sequence ID.

An antenna port is defined such that the channel over which a symbol onthe antenna port is conveyed can be inferred from the channel over whichanother symbol on the same antenna port is conveyed. If a first symboland a second symbol are transmitted on the same antenna port, thereceiver may infer the channel (e.g., fading gain, multipath delay,and/or the like) for conveying the second symbol on the antenna port,from the channel for conveying the first symbol on the antenna port. Afirst antenna port and a second antenna port may be referred to as quasico-located (QCLed) if one or more large-scale properties of the channelover which a first symbol on the first antenna port is conveyed may beinferred from the channel over which a second symbol on a second antennaport is conveyed. The one or more large-scale properties may comprise atleast one of: a delay spread; a Doppler spread; a Doppler shift; anaverage gain; an average delay; and/or spatial Receiving (Rx)parameters.

Channels that use beamforming require beam management. Beam managementmay comprise beam measurement, beam selection, and beam indication. Abeam may be associated with one or more reference signals. For example,a beam may be identified by one or more beamformed reference signals.The UE may perform downlink beam measurement based on downlink referencesignals (e.g., a channel state information reference signal (CSI-RS))and generate a beam measurement report. The UE may perform the downlinkbeam measurement procedure after an RRC connection is set up with a basestation.

FIG. 11B illustrates an example of channel state information referencesignals (CSI-RS s) that are mapped in the time and frequency domains. Asquare shown in FIG. 11B may span a resource block (RB) within abandwidth of a cell. A base station may transmit one or more RRCmessages comprising CSI-RS resource configuration parameters indicatingone or more CSI-RSs. One or more of the following parameters may beconfigured by higher layer signaling (e.g., RRC and/or MAC signaling)for a CSI-RS resource configuration: a CSI-RS resource configurationidentity, a number of CSI-RS ports, a CSI-RS configuration (e.g., symboland resource element (RE) locations in a subframe), a CSI-RS subframeconfiguration (e.g., subframe location, offset, and periodicity in aradio frame), a CSI-RS power parameter, a CSI-RS sequence parameter, acode division multiplexing (CDM) type parameter, a frequency density, atransmission comb, quasi co-location (QCL) parameters (e.g.,QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist,csi-rs-configZPid, qcl-csi-rs-configNZPid), and/or other radio resourceparameters.

The three beams illustrated in FIG. 11B may be configured for a UE in aUE-specific configuration. Three beams are illustrated in FIG. 11B (beam#1, beam #2, and beam #3), more or fewer beams may be configured. Beam#1 may be allocated with CSI-RS 1101 that may be transmitted in one ormore subcarriers in an RB of a first symbol. Beam #2 may be allocatedwith CSI-RS 1102 that may be transmitted in one or more subcarriers inan RB of a second symbol. Beam #3 may be allocated with CSI-RS 1103 thatmay be transmitted in one or more subcarriers in an RB of a thirdsymbol. By using frequency division multiplexing (FDM), a base stationmay use other subcarriers in a same RB (for example, those that are notused to transmit CSI-RS 1101) to transmit another CSI-RS associated witha beam for another UE. By using time domain multiplexing (TDM), beamsused for the UE may be configured such that beams for the UE use symbolsfrom beams of other UEs.

CSI-RSs such as those illustrated in FIG. 11B (e.g., CSI-RS 1101, 1102,1103) may be transmitted by the base station and used by the UE for oneor more measurements. For example, the UE may measure a reference signalreceived power (RSRP) of configured CSI-RS resources. The base stationmay configure the UE with a reporting configuration and the UE mayreport the RSRP measurements to a network (for example, via one or morebase stations) based on the reporting configuration. In an example, thebase station may determine, based on the reported measurement results,one or more transmission configuration indication (TCI) statescomprising a number of reference signals. In an example, the basestation may indicate one or more TCI states to the UE (e.g., via RRCsignaling, a MAC CE, and/or a DCI). The UE may receive a downlinktransmission with a receive (Rx) beam determined based on the one ormore TCI states. In an example, the UE may or may not have a capabilityof beam correspondence. If the UE has the capability of beamcorrespondence, the UE may determine a spatial domain filter of atransmit (Tx) beam based on a spatial domain filter of the correspondingRx beam. If the UE does not have the capability of beam correspondence,the UE may perform an uplink beam selection procedure to determine thespatial domain filter of the Tx beam. The UE may perform the uplink beamselection procedure based on one or more sounding reference signal (SRS)resources configured to the UE by the base station. The base station mayselect and indicate uplink beams for the UE based on measurements of theone or more SRS resources transmitted by the UE.

In a beam management procedure, a UE may assess (e.g., measure) achannel quality of one or more beam pair links, a beam pair linkcomprising a transmitting beam transmitted by a base station and areceiving beam received by the UE. Based on the assessment, the UE maytransmit a beam measurement report indicating one or more beam pairquality parameters comprising, e.g., one or more beam identifications(e.g., a beam index, a reference signal index, or the like), RSRP, aprecoding matrix indicator (PMI), a channel quality indicator (CQI),and/or a rank indicator (RI).

FIG. 12A illustrates examples of three downlink beam managementprocedures: P1, P2, and P3. Procedure P1 may enable a UE measurement ontransmit (Tx) beams of a transmission reception point (TRP) (or multipleTRPs), e.g., to support a selection of one or more base station Tx beamsand/or UE Rx beams (shown as ovals in the top row and bottom row,respectively, of P1). Beamforming at a TRP may comprise a Tx beam sweepfor a set of beams (shown, in the top rows of P1 and P2, as ovalsrotated in a counter-clockwise direction indicated by the dashed arrow).Beamforming at a UE may comprise an Rx beam sweep for a set of beams(shown, in the bottom rows of P1 and P3, as ovals rotated in a clockwisedirection indicated by the dashed arrow). Procedure P2 may be used toenable a UE measurement on Tx beams of a TRP (shown, in the top row ofP2, as ovals rotated in a counter-clockwise direction indicated by thedashed arrow). The UE and/or the base station may perform procedure P2using a smaller set of beams than is used in procedure P1, or usingnarrower beams than the beams used in procedure P1. This may be referredto as beam refinement. The UE may perform procedure P3 for Rx beamdetermination by using the same Tx beam at the base station and sweepingan Rx beam at the UE.

FIG. 12B illustrates examples of three uplink beam managementprocedures: U1, U2, and U3. Procedure U1 may be used to enable a basestation to perform a measurement on Tx beams of a UE, e.g., to support aselection of one or more UE Tx beams and/or base station Rx beams (shownas ovals in the top row and bottom row, respectively, of U1).Beamforming at the UE may include, e.g., a Tx beam sweep from a set ofbeams (shown in the bottom rows of U1 and U3 as ovals rotated in aclockwise direction indicated by the dashed arrow). Beamforming at thebase station may include, e.g., an Rx beam sweep from a set of beams(shown, in the top rows of U1 and U2, as ovals rotated in acounter-clockwise direction indicated by the dashed arrow). Procedure U2may be used to enable the base station to adjust its Rx beam when the UEuses a fixed Tx beam. The UE and/or the base station may performprocedure U2 using a smaller set of beams than is used in procedure P1,or using narrower beams than the beams used in procedure P1. This may bereferred to as beam refinement The UE may perform procedure U3 to adjustits Tx beam when the base station uses a fixed Rx beam.

A UE may initiate a beam failure recovery (BFR) procedure based ondetecting a beam failure. The UE may transmit a BFR request (e.g., apreamble, a UCI, an SR, a MAC CE, and/or the like) based on theinitiating of the BFR procedure. The UE may detect the beam failurebased on a determination that a quality of beam pair link(s) of anassociated control channel is unsatisfactory (e.g., having an error ratehigher than an error rate threshold, a received signal power lower thana received signal power threshold, an expiration of a timer, and/or thelike).

The UE may measure a quality of a beam pair link using one or morereference signals (RSs) comprising one or more SS/PBCH blocks, one ormore CSI-RS resources, and/or one or more demodulation reference signals(DMRSs). A quality of the beam pair link may be based on one or more ofa block error rate (BLER), an RSRP value, a signal to interference plusnoise ratio (SINR) value, a reference signal received quality (SEQ)value, and/or a CSI value measured on RS resources. The base station mayindicate that an RS resource is quasi co-located (QCLed) with one ormore DM-RSs of a channel (e.g., a control channel, a shared datachannel, and/or the like). The RS resource and the one or more DMRSs ofthe channel may be QCLed when the channel characteristics (e.g., Dopplershift, Doppler spread, average delay, delay spread, spatial Rxparameter, fading, and/or the like) from a transmission via the RSresource to the UE are similar or the same as the channelcharacteristics from a transmission via the channel to the UE.

A network (e.g., a gNB and/or an ng-eNB of a network) and/or the UE mayinitiate a random access procedure. A UE in an RRC_IDLE state and/or anRRC_INACTIVE state may initiate the random access procedure to request aconnection setup to a network. The UE may initiate the random accessprocedure from an RRC_CONNECTED state. The UE may initiate the randomaccess procedure to request uplink resources (e.g., for uplinktransmission of an SR when there is no PUCCH resource available) and/oracquire uplink timing (e.g., when uplink synchronization status isnon-synchronized). The UE may initiate the random access procedure torequest one or more system information blocks (SIBs) (e.g., other systeminformation such as SIB2, SIB3, and/or the like). The UE may initiatethe random access procedure for a beam failure recovery request. Anetwork may initiate a random access procedure for a handover and/or forestablishing time alignment for an SCell addition.

FIG. 13A illustrates a four-step contention-based random accessprocedure. Prior to initiation of the procedure, a base station maytransmit a configuration message 1310 to the UE. The procedureillustrated in FIG. 13A comprises transmission of four messages: a Msg 11311, a Msg 2 1312, a Msg 3 1313, and a Msg 4 1314. The Msg 1 1311 mayinclude and/or be referred to as a preamble (or a random accesspreamble). The Msg 2 1312 may include and/or be referred to as a randomaccess response (RAR).

The configuration message 1310 may be transmitted, for example, usingone or more RRC messages. The one or more RRC messages may indicate oneor more random access channel (RACH) parameters to the UE. The one ormore RACH parameters may comprise at least one of following: generalparameters for one or more random access procedures (e.g.,RACH-configGeneral); cell-specific parameters (e.g., RACH-ConfigCommon);and/or dedicated parameters (e.g., RACH-configDedicated). The basestation may broadcast or multicast the one or more RRC messages to oneor more UEs. The one or more RRC messages may be UE-specific (e.g.,dedicated RRC messages transmitted to a UE in an RRC_CONNECTED stateand/or in an RRC_INACTIVE state). The UE may determine, based on the oneor more RACH parameters, a time-frequency resource and/or an uplinktransmit power for transmission of the Msg 1 1311 and/or the Msg 3 1313.Based on the one or more RACH parameters, the UE may determine areception timing and a downlink channel for receiving the Msg 2 1312 andthe Msg 4 1314.

The one or more RACH parameters provided in the configuration message1310 may indicate one or more Physical RACH (PRACH) occasions availablefor transmission of the Msg 1 1311. The one or more PRACH occasions maybe predefined. The one or more RACH parameters may indicate one or moreavailable sets of one or more PRACH occasions (e.g., prach-ConfigIndex).The one or more RACH parameters may indicate an association between (a)one or more PRACH occasions and (b) one or more reference signals. Theone or more RACH parameters may indicate an association between (a) oneor more preambles and (b) one or more reference signals. The one or morereference signals may be SS/PBCH blocks and/or CSI-RSs. For example, theone or more RACH parameters may indicate a number of SS/PBCH blocksmapped to a PRACH occasion and/or a number of preambles mapped to aSS/PBCH blocks.

The one or more RACH parameters provided in the configuration message1310 may be used to determine an uplink transmit power of Msg 1 1311and/or Msg 3 1313. For example, the one or more RACH parameters mayindicate a reference power for a preamble transmission (e.g., a receivedtarget power and/or an initial power of the preamble transmission).There may be one or more power offsets indicated by the one or more RACHparameters. For example, the one or more RACH parameters may indicate: apower ramping step; a power offset between SSB and CSI-RS; a poweroffset between transmissions of the Msg 1 1311 and the Msg 3 1313;and/or a power offset value between preamble groups. The one or moreRACH parameters may indicate one or more thresholds based on which theUE may determine at least one reference signal (e.g., an SSB and/orCSI-RS) and/or an uplink carrier (e.g., a normal uplink (NUL) carrierand/or a supplemental uplink (SUL) carrier).

The Msg 1 1311 may include one or more preamble transmissions (e.g., apreamble transmission and one or more preamble retransmissions). An RRCmessage may be used to configure one or more preamble groups (e.g.,group A and/or group B). A preamble group may comprise one or morepreambles. The UE may determine the preamble group based on a pathlossmeasurement and/or a size of the Msg 3 1313. The UE may measure an RSRPof one or more reference signals (e.g., SSBs and/or CSI-RSs) anddetermine at least one reference signal having an RSRP above an RSRPthreshold (e.g., rsrp-ThresholdSSB and/or rsrp-ThresholdCSI-RS). The UEmay select at least one preamble associated with the one or morereference signals and/or a selected preamble group, for example, if theassociation between the one or more preambles and the at least onereference signal is configured by an RRC message.

The UE may determine the preamble based on the one or more RACHparameters provided in the configuration message 1310. For example, theUE may determine the preamble based on a pathloss measurement, an RSRPmeasurement, and/or a size of the Msg 3 1313. As another example, theone or more RACH parameters may indicate: a preamble format; a maximumnumber of preamble transmissions; and/or one or more thresholds fordetermining one or more preamble groups (e.g., group A and group B). Abase station may use the one or more RACH parameters to configure the UEwith an association between one or more preambles and one or morereference signals (e.g., SSBs and/or CSI-RSs). If the association isconfigured, the UE may determine the preamble to include in Msg 1 1311based on the association. The Msg 1 1311 may be transmitted to the basestation via one or more PRACH occasions. The UE may use one or morereference signals (e.g., SSBs and/or CSI-RSs) for selection of thepreamble and for determining of the PRACH occasion. One or more RACHparameters (e.g., ra-ssb-OccasionMskIndex and/or ra-OccasionList) mayindicate an association between the PRACH occasions and the one or morereference signals.

The UE may perform a preamble retransmission if no response is receivedfollowing a preamble transmission. The UE may increase an uplinktransmit power for the preamble retransmission. The UE may select aninitial preamble transmit power based on a pathloss measurement and/or atarget received preamble power configured by the network. The UE maydetermine to retransmit a preamble and may ramp up the uplink transmitpower. The UE may receive one or more RACH parameters (e.g.,PREAMBLE_POWER_RAMPING_STEP) indicating a ramping step for the preambleretransmission. The ramping step may be an amount of incrementalincrease in uplink transmit power for a retransmission. The UE may rampup the uplink transmit power if the UE determines a reference signal(e.g., SSB and/or CSI-RS) that is the same as a previous preambletransmission. The UE may count a number of preamble transmissions and/orretransmissions (e.g., PREAMBLE_TRANSMISSION_COUNTER). The UE maydetermine that a random access procedure completed unsuccessfully, forexample, if the number of preamble transmissions exceeds a thresholdconfigured by the one or more RACH parameters (e.g., preambleTransMax).

The Msg 2 1312 received by the UE may include an RAR. In some scenarios,the Msg 2 1312 may include multiple RARs corresponding to multiple UEs.The Msg 2 1312 may be received after or in response to the transmittingof the Msg 1 1311. The Msg 2 1312 may be scheduled on the DL-SCH andindicated on a PDCCH using a random access RNTI (RA-RNTI). The Msg 21312 may indicate that the Msg 1 1311 was received by the base station.The Msg 2 1312 may include a time-alignment command that may be used bythe UE to adjust the UE's transmission timing, a scheduling grant fortransmission of the Msg 3 1313, and/or a Temporary Cell RNTI (TC-RNTI).After transmitting a preamble, the UE may start a time window (e.g.,ra-ResponseWindow) to monitor a PDCCH for the Msg 2 1312. The UE maydetermine when to start the time window based on a PRACH occasion thatthe UE uses to transmit the preamble. For example, the UE may start thetime window one or more symbols after a last symbol of the preamble(e.g., at a first PDCCH occasion from an end of a preambletransmission). The one or more symbols may be determined based on anumerology. The PDCCH may be in a common search space (e.g., aType1-PDCCH common search space) configured by an RRC message. The UEmay identify the RAR based on a Radio Network Temporary Identifier(RNTI). RNTIs may be used depending on one or more events initiating therandom access procedure. The UE may use random access RNTI (RA-RNTI).The RA-RNTI may be associated with PRACH occasions in which the UEtransmits a preamble. For example, the UE may determine the RA-RNTIbased on: an OFDM symbol index; a slot index; a frequency domain index;and/or a UL carrier indicator of the PRACH occasions. An example ofRA-RNTI may be as follows:

RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id

where s_id may be an index of a first OFDM symbol of the PRACH occasion(e.g., 0≤s_id<14), t_id may be an index of a first slot of the PRACHoccasion in a system frame (e.g., 0≤t_id<80), fid may be an index of thePRACH occasion in the frequency domain (e.g., 0≤f_id<8), andul_carrier_id may be a UL carrier used for a preamble transmission(e.g., 0 for an NUL carrier, and 1 for an SUL carrier).The UE may transmit the Msg 3 1313 in response to a successful receptionof the Msg 2 1312 (e.g., using resources identified in the Msg 2 1312).The Msg 3 1313 may be used for contention resolution in, for example,the contention-based random access procedure illustrated in FIG. 13A. Insome scenarios, a plurality of UEs may transmit a same preamble to abase station and the base station may provide an RAR that corresponds toa UE. Collisions may occur if the plurality of UEs interpret the RAR ascorresponding to themselves. Contention resolution (e.g., using the Msg3 1313 and the Msg 4 1314) may be used to increase the likelihood thatthe UE does not incorrectly use an identity of another the UE. Toperform contention resolution, the UE may include a device identifier inthe Msg 3 1313 (e.g., a C-RNTI if assigned, a TC-RNTI included in theMsg 2 1312, and/or any other suitable identifier).

The Msg 4 1314 may be received after or in response to the transmittingof the Msg 3 1313. If a C-RNTI was included in the Msg 3 1313, the basestation will address the UE on the PDCCH using the C-RNTI. If the UE'sunique C-RNTI is detected on the PDCCH, the random access procedure isdetermined to be successfully completed. If a TC-RNTI is included in theMsg 3 1313 (e.g., if the UE is in an RRC_IDLE state or not otherwiseconnected to the base station), Msg 4 1314 will be received using aDL-SCH associated with the TC-RNTI. If a MAC PDU is successfully decodedand a MAC PDU comprises the UE contention resolution identity MAC CEthat matches or otherwise corresponds with the CCCH SDU sent (e.g.,transmitted) in Msg 3 1313, the UE may determine that the contentionresolution is successful and/or the UE may determine that the randomaccess procedure is successfully completed.

The UE may be configured with a supplementary uplink (SUL) carrier and anormal uplink (NUL) carrier. An initial access (e.g., random accessprocedure) may be supported in an uplink carrier. For example, a basestation may configure the UE with two separate RACH configurations: onefor an SUL carrier and the other for an NUL carrier. For random accessin a cell configured with an SUL carrier, the network may indicate whichcarrier to use (NUL or SUL). The UE may determine the SUL carrier, forexample, if a measured quality of one or more reference signals is lowerthan a broadcast threshold. Uplink transmissions of the random accessprocedure (e.g., the Msg 1 1311 and/or the Msg 3 1313) may remain on theselected carrier. The UE may switch an uplink carrier during the randomaccess procedure (e.g., between the Msg 1 1311 and the Msg 3 1313) inone or more cases. For example, the UE may determine and/or switch anuplink carrier for the Msg 1 1311 and/or the Msg 3 1313 based on achannel clear assessment (e.g., a listen-before-talk).

FIG. 13B illustrates a two-step contention-free random access procedure.Similar to the four-step contention-based random access procedureillustrated in FIG. 13A, a base station may, prior to initiation of theprocedure, transmit a configuration message 1320 to the UE. Theconfiguration message 1320 may be analogous in some respects to theconfiguration message 1310. The procedure illustrated in FIG. 13Bcomprises transmission of two messages: a Msg 1 1321 and a Msg 2 1322.The Msg 1 1321 and the Msg 2 1322 may be analogous in some respects tothe Msg 1 1311 and a Msg 2 1312 illustrated in FIG. 13A, respectively.As will be understood from FIGS. 13A and 13B, the contention-free randomaccess procedure may not include messages analogous to the Msg 3 1313and/or the Msg 4 1314.

The contention-free random access procedure illustrated in FIG. 13B maybe initiated for a beam failure recovery, other SI request, SCelladdition, and/or handover. For example, a base station may indicate orassign to the UE the preamble to be used for the Msg 1 1321. The UE mayreceive, from the base station via PDCCH and/or RRC, an indication of apreamble (e.g., ra-PreambleIndex).

After transmitting a preamble, the UE may start a time window (e.g.,ra-ResponseWindow) to monitor a PDCCH for the RAR. In the event of abeam failure recovery request, the base station may configure the UEwith a separate time window and/or a separate PDCCH in a search spaceindicated by an RRC message (e.g., recoverySearchSpaceId). The UE maymonitor for a PDCCH transmission addressed to a Cell RNTI (C-RNTI) onthe search space. In the contention-free random access procedureillustrated in FIG. 13B, the UE may determine that a random accessprocedure successfully completes after or in response to transmission ofMsg 1 1321 and reception of a corresponding Msg 2 1322. The UE maydetermine that a random access procedure successfully completes, forexample, if a PDCCH transmission is addressed to a C-RNTI. The UE maydetermine that a random access procedure successfully completes, forexample, if the UE receives an RAR comprising a preamble identifiercorresponding to a preamble transmitted by the UE and/or the RARcomprises a MAC sub-PDU with the preamble identifier. The UE maydetermine the response as an indication of an acknowledgement for an SIrequest.

FIG. 13C illustrates another two-step random access procedure. Similarto the random access procedures illustrated in FIGS. 13A and 13B, a basestation may, prior to initiation of the procedure, transmit aconfiguration message 1330 to the UE. The configuration message 1330 maybe analogous in some respects to the configuration message 1310 and/orthe configuration message 1320. The procedure illustrated in FIG. 13Ccomprises transmission of two messages: a Msg A 1331 and a Msg B 1332.

Msg A 1331 may be transmitted in an uplink transmission by the UE. Msg A1331 may comprise one or more transmissions of a preamble 1341 and/orone or more transmissions of a transport block 1342. The transport block1342 may comprise contents that are similar and/or equivalent to thecontents of the Msg 3 1313 illustrated in FIG. 13A. The transport block1342 may comprise UCI (e.g., an SR, a HARQ ACK/NACK, and/or the like).The UE may receive the Msg B 1332 after or in response to transmittingthe Msg A 1331. The Msg B 1332 may comprise contents that are similarand/or equivalent to the contents of the Msg 2 1312 (e.g., an RAR)illustrated in FIGS. 13A and 13B and/or the Msg 4 1314 illustrated inFIG. 13A.

The UE may initiate the two-step random access procedure in FIG. 13C forlicensed spectrum and/or unlicensed spectrum. The UE may determine,based on one or more factors, whether to initiate the two-step randomaccess procedure. The one or more factors may be: a radio accesstechnology in use (e.g., LTE, NR, and/or the like); whether the UE hasvalid TA or not; a cell size; the UE's RRC state; a type of spectrum(e.g., licensed vs. unlicensed); and/or any other suitable factors.

The UE may determine, based on two-step RACH parameters included in theconfiguration message 1330, a radio resource and/or an uplink transmitpower for the preamble 1341 and/or the transport block 1342 included inthe Msg A 1331. The RACH parameters may indicate a modulation and codingschemes (MCS), a time-frequency resource, and/or a power control for thepreamble 1341 and/or the transport block 1342. A time-frequency resourcefor transmission of the preamble 1341 (e.g., a PRACH) and atime-frequency resource for transmission of the transport block 1342(e.g., a PUSCH) may be multiplexed using FDM, TDM, and/or CDM. The RACHparameters may enable the UE to determine a reception timing and adownlink channel for monitoring for and/or receiving Msg B 1332.

The transport block 1342 may comprise data (e.g., delay-sensitive data),an identifier of the UE, security information, and/or device information(e.g., an International Mobile Subscriber Identity (IMSI)). The basestation may transmit the Msg B 1332 as a response to the Msg A 1331. TheMsg B 1332 may comprise at least one of following: a preambleidentifier; a timing advance command; a power control command; an uplinkgrant (e.g., a radio resource assignment and/or an MCS); a UE identifierfor contention resolution; and/or an RNTI (e.g., a C-RNTI or a TC-RNTI).The UE may determine that the two-step random access procedure issuccessfully completed if: a preamble identifier in the Msg B 1332 ismatched to a preamble transmitted by the UE; and/or the identifier ofthe UE in Msg B 1332 is matched to the identifier of the UE in the Msg A1331 (e.g., the transport block 1342).

A UE and a base station may exchange control signaling. The controlsignaling may be referred to as L1/L2 control signaling and mayoriginate from the PHY layer (e.g., layer 1) and/or the MAC layer (e.g.,layer 2). The control signaling may comprise downlink control signalingtransmitted from the base station to the UE and/or uplink controlsignaling transmitted from the UE to the base station.

The downlink control signaling may comprise: a downlink schedulingassignment; an uplink scheduling grant indicating uplink radio resourcesand/or a transport format; a slot format information; a preemptionindication; a power control command; and/or any other suitablesignaling. The UE may receive the downlink control signaling in apayload transmitted by the base station on a physical downlink controlchannel (PDCCH). The payload transmitted on the PDCCH may be referred toas downlink control information (DCI). In some scenarios, the PDCCH maybe a group common PDCCH (GC-PDCCH) that is common to a group of UEs.

A base station may attach one or more cyclic redundancy check (CRC)parity bits to a DCI in order to facilitate detection of transmissionerrors. When the DCI is intended for a UE (or a group of the UEs), thebase station may scramble the CRC parity bits with an identifier of theUE (or an identifier of the group of the UEs). Scrambling the CRC paritybits with the identifier may comprise Modulo-2 addition (or an exclusiveOR operation) of the identifier value and the CRC parity bits. Theidentifier may comprise a 16-bit value of a radio network temporaryidentifier (RNTI).

DCIs may be used for different purposes. A purpose may be indicated bythe type of RNTI used to scramble the CRC parity bits. For example, aDCI having CRC parity bits scrambled with a paging RNTI (P-RNTI) mayindicate paging information and/or a system information changenotification. The P-RNTI may be predefined as “FFFE” in hexadecimal. ADCI having CRC parity bits scrambled with a system information RNTI(SI-RNTI) may indicate a broadcast transmission of the systeminformation. The SI-RNTI may be predefined as “FFFF” in hexadecimal. ADCI having CRC parity bits scrambled with a random access RNTI (RA-RNTI)may indicate a random access response (RAR). A DCI having CRC paritybits scrambled with a cell RNTI (C-RNTI) may indicate a dynamicallyscheduled unicast transmission and/or a triggering of PDCCH-orderedrandom access. A DCI having CRC parity bits scrambled with a temporarycell RNTI (TC-RNTI) may indicate a contention resolution (e.g., a Msg 3analogous to the Msg 3 1313 illustrated in FIG. 13A). Other RNTIsconfigured to the UE by a base station may comprise a ConfiguredScheduling RNTI (CS-RNTI), a Transmit Power Control-PUCCH RNTI(TPC-PUCCH-RNTI), a Transmit Power Control-PUSCH RNTI (TPC-PUSCH-RNTI),a Transmit Power Control-SRS RNTI (TPC-SRS-RNTI), an Interruption RNTI(INT-RNTI), a Slot Format Indication RNTI (SFI-RNTI), a Semi-PersistentCSI RNTI (SP-CSI-RNTI), a Modulation and Coding Scheme Cell RNTI(MCS-C-RNTI), and/or the like.

Depending on the purpose and/or content of a DCI, the base station maytransmit the DCIs with one or more DCI formats. For example, DCI format0_0 may be used for scheduling of PUSCH in a cell. DCI format 0_0 may bea fallback DCI format (e.g., with compact DCI payloads). DCI format 0_1may be used for scheduling of PUSCH in a cell (e.g., with more DCIpayloads than DCI format 0_0). DCI format 1_0 may be used for schedulingof PDSCH in a cell. DCI format 1_0 may be a fallback DCI format (e.g.,with compact DCI payloads). DCI format 1_1 may be used for scheduling ofPDSCH in a cell (e.g., with more DCI payloads than DCI format 1_0). DCIformat 2_0 may be used for providing a slot format indication to a groupof UEs. DCI format 2_1 may be used for notifying a group of UEs of aphysical resource block and/or OFDM symbol where the UE may assume notransmission is intended to the UE. DCI format 2_2 may be used fortransmission of a transmit power control (TPC) command for PUCCH orPUSCH. DCI format 2_3 may be used for transmission of a group of TPCcommands for SRS transmissions by one or more UEs. DCI format(s) for newfunctions may be defined in future releases. DCI formats may havedifferent DCI sizes, or may share the same DCI size.

After scrambling a DCI with a RNTI, the base station may process the DCIwith channel coding (e.g., polar coding), rate matching, scramblingand/or QPSK modulation. A base station may map the coded and modulatedDCI on resource elements used and/or configured for a PDCCH. Based on apayload size of the DCI and/or a coverage of the base station, the basestation may transmit the DCI via a PDCCH occupying a number ofcontiguous control channel elements (CCEs). The number of the contiguousCCEs (referred to as aggregation level) may be 1, 2, 4, 8, 16, and/orany other suitable number. A CCE may comprise a number (e.g., 6) ofresource-element groups (REGs). A REG may comprise a resource block inan OFDM symbol. The mapping of the coded and modulated DCI on theresource elements may be based on mapping of CCEs and REGs (e.g.,CCE-to-REG mapping).

FIG. 14A illustrates an example of CORESET configurations for abandwidth part. The base station may transmit a DCI via a PDCCH on oneor more control resource sets (CORESETs). A CORESET may comprise atime-frequency resource in which the UE tries to decode a DCI using oneor more search spaces. The base station may configure a CORESET in thetime-frequency domain. In the example of FIG. 14A, a first CORESET 1401and a second CORESET 1402 occur at the first symbol in a slot. The firstCORESET 1401 overlaps with the second CORESET 1402 in the frequencydomain. A third CORESET 1403 occurs at a third symbol in the slot. Afourth CORESET 1404 occurs at the seventh symbol in the slot. CORESETsmay have a different number of resource blocks in frequency domain.

FIG. 14B illustrates an example of a CCE-to-REG mapping for DCItransmission on a CORESET and PDCCH processing. The CCE-to-REG mappingmay be an interleaved mapping (e.g., for the purpose of providingfrequency diversity) or a non-interleaved mapping (e.g., for thepurposes of facilitating interference coordination and/orfrequency-selective transmission of control channels). The base stationmay perform different or same CCE-to-REG mapping on different CORESETs.A CORESET may be associated with a CCE-to-REG mapping by RRCconfiguration. A CORESET may be configured with an antenna port quasico-location (QCL) parameter. The antenna port QCL parameter may indicateQCL information of a demodulation reference signal (DMRS) for PDCCHreception in the CORESET.

The base station may transmit, to the UE, RRC messages comprisingconfiguration parameters of one or more CORESETs and one or more searchspace sets. The configuration parameters may indicate an associationbetween a search space set and a CORESET. A search space set maycomprise a set of PDCCH candidates formed by CCEs at a given aggregationlevel. The configuration parameters may indicate: a number of PDCCHcandidates to be monitored per aggregation level; a PDCCH monitoringperiodicity and a PDCCH monitoring pattern; one or more DCI formats tobe monitored by the UE; and/or whether a search space set is a commonsearch space set or a UE-specific search space set. A set of CCEs in thecommon search space set may be predefined and known to the UE. A set ofCCEs in the UE-specific search space set may be configured based on theUE's identity (e.g., C-RNTI).

As shown in FIG. 14B, the UE may determine a time-frequency resource fora CORESET based on RRC messages. The UE may determine a CCE-to-REGmapping (e.g., interleaved or non-interleaved, and/or mappingparameters) for the CORESET based on configuration parameters of theCORESET. The UE may determine a number (e.g., at most 10) of searchspace sets configured on the CORESET based on the RRC messages. The UEmay monitor a set of PDCCH candidates according to configurationparameters of a search space set. The UE may monitor a set of PDCCHcandidates in one or more CORESETs for detecting one or more DCIs.Monitoring may comprise decoding one or more PDCCH candidates of the setof the PDCCH candidates according to the monitored DCI formats.Monitoring may comprise decoding a DCI content of one or more PDCCHcandidates with possible (or configured) PDCCH locations, possible (orconfigured) PDCCH formats (e.g., number of CCEs, number of PDCCHcandidates in common search spaces, and/or number of PDCCH candidates inthe UE-specific search spaces) and possible (or configured) DCI formats.The decoding may be referred to as blind decoding. The UE may determinea DCI as valid for the UE, in response to CRC checking (e.g., scrambledbits for CRC parity bits of the DCI matching a RNTI value). The UE mayprocess information contained in the DCI (e.g., a scheduling assignment,an uplink grant, power control, a slot format indication, a downlinkpreemption, and/or the like).

The UE may transmit uplink control signaling (e.g., uplink controlinformation (UCI)) to a base station. The uplink control signaling maycomprise hybrid automatic repeat request (HARQ) acknowledgements forreceived DL-SCH transport blocks. The UE may transmit the HARQacknowledgements after receiving a DL-SCH transport block. Uplinkcontrol signaling may comprise channel state information (CSI)indicating channel quality of a physical downlink channel. The UE maytransmit the CSI to the base station. The base station, based on thereceived CSI, may determine transmission format parameters (e.g.,comprising multi-antenna and beamforming schemes) for a downlinktransmission. Uplink control signaling may comprise scheduling requests(SR). The UE may transmit an SR indicating that uplink data is availablefor transmission to the base station. The UE may transmit a UCI (e.g.,HARQ acknowledgements (HARQ-ACK), CSI report, SR, and the like) via aphysical uplink control channel (PUCCH) or a physical uplink sharedchannel (PUSCH). The UE may transmit the uplink control signaling via aPUCCH using one of several PUCCH formats.

There may be five PUCCH formats and the UE may determine a PUCCH formatbased on a size of the UCI (e.g., a number of uplink symbols of UCItransmission and a number of UCI bits). PUCCH format 0 may have a lengthof one or two OFDM symbols and may include two or fewer bits. The UE maytransmit UCI in a PUCCH resource using PUCCH format 0 if thetransmission is over one or two symbols and the number of HARQ-ACKinformation bits with positive or negative SR (HARQ-ACK/SR bits) is oneor two. PUCCH format 1 may occupy a number between four and fourteenOFDM symbols and may include two or fewer bits. The UE may use PUCCHformat 1 if the transmission is four or more symbols and the number ofHARQ-ACK/SR bits is one or two. PUCCH format 2 may occupy one or twoOFDM symbols and may include more than two bits. The UE may use PUCCHformat 2 if the transmission is over one or two symbols and the numberof UCI bits is two or more. PUCCH format 3 may occupy a number betweenfour and fourteen OFDM symbols and may include more than two bits. TheUE may use PUCCH format 3 if the transmission is four or more symbols,the number of UCI bits is two or more and PUCCH resource does notinclude an orthogonal cover code. PUCCH format 4 may occupy a numberbetween four and fourteen OFDM symbols and may include more than twobits. The UE may use PUCCH format 4 if the transmission is four or moresymbols, the number of UCI bits is two or more and the PUCCH resourceincludes an orthogonal cover code.

The base station may transmit configuration parameters to the UE for aplurality of PUCCH resource sets using, for example, an RRC message. Theplurality of PUCCH resource sets (e.g., up to four sets) may beconfigured on an uplink BWP of a cell. A PUCCH resource set may beconfigured with a PUCCH resource set index, a plurality of PUCCHresources with a PUCCH resource being identified by a PUCCH resourceidentifier (e.g., pucch-Resourceid), and/or a number (e.g. a maximumnumber) of UCI information bits the UE may transmit using one of theplurality of PUCCH resources in the PUCCH resource set. When configuredwith a plurality of PUCCH resource sets, the UE may select one of theplurality of PUCCH resource sets based on a total bit length of the UCIinformation bits (e.g., HARQ-ACK, SR, and/or CSI). If the total bitlength of UCI information bits is two or fewer, the UE may select afirst PUCCH resource set having a PUCCH resource set index equal to “0”.If the total bit length of UCI information bits is greater than two andless than or equal to a first configured value, the UE may select asecond PUCCH resource set having a PUCCH resource set index equal to“1”. If the total bit length of UCI information bits is greater than thefirst configured value and less than or equal to a second configuredvalue, the UE may select a third PUCCH resource set having a PUCCHresource set index equal to “2”. If the total bit length of UCIinformation bits is greater than the second configured value and lessthan or equal to a third value (e.g., 1406), the UE may select a fourthPUCCH resource set having a PUCCH resource set index equal to “3”.

After determining a PUCCH resource set from a plurality of PUCCHresource sets, the UE may determine a PUCCH resource from the PUCCHresource set for UCI (HARQ-ACK, CSI, and/or SR) transmission. The UE maydetermine the PUCCH resource based on a PUCCH resource indicator in aDCI (e.g., with a DCI format 1_0 or DCI for 1_1) received on a PDCCH. Athree-bit PUCCH resource indicator in the DCI may indicate one of eightPUCCH resources in the PUCCH resource set. Based on the PUCCH resourceindicator, the UE may transmit the UCI (HARQ-ACK, CSI and/or SR) using aPUCCH resource indicated by the PUCCH resource indicator in the DCI.

FIG. 15 illustrates an example of a wireless device 1502 incommunication with a base station 1504 in accordance with embodiments ofthe present disclosure. The wireless device 1502 and base station 1504may be part of a mobile communication network, such as the mobilecommunication network 100 illustrated in FIG. 1A, the mobilecommunication network 150 illustrated in FIG. 1B, or any othercommunication network. Only one wireless device 1502 and one basestation 1504 are illustrated in FIG. 15, but it will be understood thata mobile communication network may include more than one UE and/or morethan one base station, with the same or similar configuration as thoseshown in FIG. 15.

The base station 1504 may connect the wireless device 1502 to a corenetwork (not shown) through radio communications over the air interface(or radio interface) 1506. The communication direction from the basestation 1504 to the wireless device 1502 over the air interface 1506 isknown as the downlink, and the communication direction from the wirelessdevice 1502 to the base station 1504 over the air interface is known asthe uplink. Downlink transmissions may be separated from uplinktransmissions using FDD, TDD, and/or some combination of the twoduplexing techniques.

In the downlink, data to be sent to the wireless device 1502 from thebase station 1504 may be provided to the processing system 1508 of thebase station 1504. The data may be provided to the processing system1508 by, for example, a core network. In the uplink, data to be sent tothe base station 1504 from the wireless device 1502 may be provided tothe processing system 1518 of the wireless device 1502. The processingsystem 1508 and the processing system 1518 may implement layer 3 andlayer 2 OSI functionality to process the data for transmission. Layer 2may include an SDAP layer, a PDCP layer, an RLC layer, and a MAC layer,for example, with respect to FIG. 2A, FIG. 2B, FIG. 3, and FIG. 4A.Layer 3 may include an RRC layer as with respect to FIG. 2B.

After being processed by processing system 1508, the data to be sent tothe wireless device 1502 may be provided to a transmission processingsystem 1510 of base station 1504. Similarly, after being processed bythe processing system 1518, the data to be sent to base station 1504 maybe provided to a transmission processing system 1520 of the wirelessdevice 1502. The transmission processing system 1510 and thetransmission processing system 1520 may implement layer 1 OSIfunctionality. Layer 1 may include a PHY layer with respect to FIG. 2A,FIG. 2B, FIG. 3, and FIG. 4A. For transmit processing, the PHY layer mayperform, for example, forward error correction coding of transportchannels, interleaving, rate matching, mapping of transport channels tophysical channels, modulation of physical channel, multiple-inputmultiple-output (MIMO) or multi-antenna processing, and/or the like.

At the base station 1504, a reception processing system 1512 may receivethe uplink transmission from the wireless device 1502. At the wirelessdevice 1502, a reception processing system 1522 may receive the downlinktransmission from base station 1504. The reception processing system1512 and the reception processing system 1522 may implement layer 1 OSIfunctionality. Layer 1 may include a PHY layer with respect to FIG. 2A,FIG. 2B, FIG. 3, and FIG. 4A. For receive processing, the PHY layer mayperform, for example, error detection, forward error correctiondecoding, deinterleaving, demapping of transport channels to physicalchannels, demodulation of physical channels, MIMO or multi-antennaprocessing, and/or the like.

As shown in FIG. 15, a wireless device 1502 and the base station 1504may include multiple antennas. The multiple antennas may be used toperform one or more MIMO or multi-antenna techniques, such as spatialmultiplexing (e.g., single-user MIMO or multi-user MIMO),transmit/receive diversity, and/or beamforming. In other examples, thewireless device 1502 and/or the base station 1504 may have a singleantenna.

The processing system 1508 and the processing system 1518 may beassociated with a memory 1514 and a memory 1524, respectively. Memory1514 and memory 1524 (e.g., one or more non-transitory computer readablemediums) may store computer program instructions or code that may beexecuted by the processing system 1508 and/or the processing system 1518to carry out one or more of the functionalities discussed in the presentapplication. Although not shown in FIG. 15, the transmission processingsystem 1510, the transmission processing system 1520, the receptionprocessing system 1512, and/or the reception processing system 1522 maybe coupled to a memory (e.g., one or more non-transitory computerreadable mediums) storing computer program instructions or code that maybe executed to carry out one or more of their respectivefunctionalities.

The processing system 1508 and/or the processing system 1518 maycomprise one or more controllers and/or one or more processors. The oneor more controllers and/or one or more processors may comprise, forexample, a general-purpose processor, a digital signal processor (DSP),a microcontroller, an application specific integrated circuit (ASIC), afield programmable gate array (FPGA) and/or other programmable logicdevice, discrete gate and/or transistor logic, discrete hardwarecomponents, an on-board unit, or any combination thereof. The processingsystem 1508 and/or the processing system 1518 may perform at least oneof signal coding/processing, data processing, power control,input/output processing, and/or any other functionality that may enablethe wireless device 1502 and the base station 1504 to operate in awireless environment.

The processing system 1508 and/or the processing system 1518 may beconnected to one or more peripherals 1516 and one or more peripherals1526, respectively. The one or more peripherals 1516 and the one or moreperipherals 1526 may include software and/or hardware that providefeatures and/or functionalities, for example, a speaker, a microphone, akeypad, a display, a touchpad, a power source, a satellite transceiver,a universal serial bus (USB) port, a hands-free headset, a frequencymodulated (FM) radio unit, a media player, an Internet browser, anelectronic control unit (e.g., for a motor vehicle), and/or one or moresensors (e.g., an accelerometer, a gyroscope, a temperature sensor, aradar sensor, a lidar sensor, an ultrasonic sensor, a light sensor, acamera, and/or the like). The processing system 1508 and/or theprocessing system 1518 may receive user input data from and/or provideuser output data to the one or more peripherals 1516 and/or the one ormore peripherals 1526. The processing system 1518 in the wireless device1502 may receive power from a power source and/or may be configured todistribute the power to the other components in the wireless device1502. The power source may comprise one or more sources of power, forexample, a battery, a solar cell, a fuel cell, or any combinationthereof. The processing system 1508 and/or the processing system 1518may be connected to a GPS chipset 1517 and a GPS chipset 1527,respectively. The GPS chipset 1517 and the GPS chipset 1527 may beconfigured to provide geographic location information of the wirelessdevice 1502 and the base station 1504, respectively.

FIG. 16A illustrates an example structure for uplink transmission. Abaseband signal representing a physical uplink shared channel mayperform one or more functions. The one or more functions may comprise atleast one of: scrambling; modulation of scrambled bits to generatecomplex-valued symbols; mapping of the complex-valued modulation symbolsonto one or several transmission layers; transform precoding to generatecomplex-valued symbols; precoding of the complex-valued symbols; mappingof precoded complex-valued symbols to resource elements; generation ofcomplex-valued time-domain Single Carrier-Frequency Division MultipleAccess (SC-FDMA) or CP-OFDM signal for an antenna port; and/or the like.In an example, when transform precoding is enabled, a SC-FDMA signal foruplink transmission may be generated. In an example, when transformprecoding is not enabled, an CP-OFDM signal for uplink transmission maybe generated by FIG. 16A. These functions are illustrated as examplesand it is anticipated that other mechanisms may be implemented invarious embodiments.

FIG. 16B illustrates an example structure for modulation andup-conversion of a baseband signal to a carrier frequency. The basebandsignal may be a complex-valued SC-FDMA or CP-OFDM baseband signal for anantenna port and/or a complex-valued Physical Random Access Channel(PRACH) baseband signal. Filtering may be employed prior totransmission.

FIG. 16C illustrates an example structure for downlink transmissions. Abaseband signal representing a physical downlink channel may perform oneor more functions. The one or more functions may comprise: scrambling ofcoded bits in a codeword to be transmitted on a physical channel;modulation of scrambled bits to generate complex-valued modulationsymbols; mapping of the complex-valued modulation symbols onto one orseveral transmission layers; precoding of the complex-valued modulationsymbols on a layer for transmission on the antenna ports; mapping ofcomplex-valued modulation symbols for an antenna port to resourceelements; generation of complex-valued time-domain OFDM signal for anantenna port; and/or the like. These functions are illustrated asexamples and it is anticipated that other mechanisms may be implementedin various embodiments.

FIG. 16D illustrates another example structure for modulation andup-conversion of a baseband signal to a carrier frequency. The basebandsignal may be a complex-valued OFDM baseband signal for an antenna port.Filtering may be employed prior to transmission.

A wireless device may receive from a base station one or more messages(e.g. RRC messages) comprising configuration parameters of a pluralityof cells (e.g. primary cell, secondary cell). The wireless device maycommunicate with at least one base station (e.g. two or more basestations in dual-connectivity) via the plurality of cells. The one ormore messages (e.g. as a part of the configuration parameters) maycomprise parameters of physical, MAC, RLC, PCDP, SDAP, RRC layers forconfiguring the wireless device. For example, the configurationparameters may comprise parameters for configuring physical and MAClayer channels, bearers, etc. For example, the configuration parametersmay comprise parameters indicating values of timers for physical, MAC,RLC, PCDP, SDAP, RRC layers, and/or communication channels.

A timer may begin running once it is started and continue running untilit is stopped or until it expires. A timer may be started if it is notrunning or restarted if it is running. A timer may be associated with avalue (e.g. the timer may be started or restarted from a value or may bestarted from zero and expire once it reaches the value). The duration ofa timer may not be updated until the timer is stopped or expires (e.g.,due to BWP switching). A timer may be used to measure a timeperiod/window for a process. When the specification refers to animplementation and procedure related to one or more timers, it will beunderstood that there are multiple ways to implement the one or moretimers. For example, it will be understood that one or more of themultiple ways to implement a timer may be used to measure a timeperiod/window for the procedure. For example, a random access responsewindow timer may be used for measuring a window of time for receiving arandom access response. In an example, instead of starting and expiry ofa random access response window timer, the time difference between twotime stamps may be used. When a timer is restarted, a process formeasurement of time window may be restarted. Other exampleimplementations may be provided to restart a measurement of a timewindow.

The amount of data traffic carried over cellular networks is expected toincrease for many years to come. The number of users/devices isincreasing, and each user/device accesses an increasing number andvariety of services, e.g. video delivery, large files, images. Thisrequires not only high capacity in the network, but also provisioning ofvery high data rates to meet customer expectations on interactivity andresponsiveness. More spectrum is therefore needed for cellular operatorsto meet the increasing demand. Considering user expectations of highdata rates along with seamless mobility, it is beneficial that morespectrum be made available for deploying macro cells as well as smallcells for cellular systems.

Striving to meet the market demands, there has been increasing interestfrom operators in deploying some complementary access utilizingunlicensed spectrum to meet the traffic growth. This is exemplified bythe large number of operator-deployed Wi-Fi networks and the 3GPPstandardization of interworking solutions with Wi-Fi, e.g., LTE/WLANinterworking. This interest indicates that unlicensed spectrum, whenpresent, may be an effective complement to licensed spectrum forcellular operators to address the traffic explosion in some scenarios,such as hotspot areas. For example, licensed assisted access (LAA)and/or new radio on unlicensed band(s) (NR-U) may offer an alternativefor operators to make use of unlicensed spectrum while managing oneradio network, thus offering new possibilities for optimizing thenetwork's efficiency.

In an example embodiment, Listen-before-talk (LBT) may be implementedfor transmission in an unlicensed cell. The unlicensed cell may bereferred to as a LAA cell and/or a NR-U cell. The unlicensed cell may beoperated as non-standalone with an anchor cell in a licensed band orstandalone without an anchor cell in a licensed band. LBT may comprise aclear channel assessment (CCA). For example, in an LBT procedure,equipment may apply a CCA before using the unlicensed cell or channel.The CCA may comprise an energy detection that determines the presence ofother signals on a channel (e.g., channel is occupied) or absence ofother signals on a channel (e.g., channel is clear). A regulation of acountry may impact the LBT procedure. For example, European and Japaneseregulations mandate the usage of LBT in the unlicensed bands, such asthe 5 GHz unlicensed band. Apart from regulatory requirements, carriersensing via LBT may be one way for fairly sharing the unlicensedspectrum among different devices and/or networks attempting to utilizethe unlicensed spectrum.

In an example embodiment, discontinuous transmission on an unlicensedband with limited maximum transmission duration may be enabled. Some ofthese functions may be supported by one or more signals to betransmitted from the beginning of a discontinuous downlink transmissionin the unlicensed band. Channel reservation may be enabled by thetransmission of signals, by an NR-U node, after or in response togaining channel access based on a successful LBT operation. Other nodesmay receive the signals (e.g., transmitted for the channel reservation)with an energy level above a certain threshold that may sense thechannel to be occupied. Functions that may need to be supported by oneor more signals for operation in unlicensed band with discontinuousdownlink transmission may comprise one or more of the following:detection of the downlink transmission in unlicensed band (includingcell identification) by wireless devices; time & frequencysynchronization of wireless devices.

In an example embodiment, downlink transmission and frame structuredesign for operation in an unlicensed band may employ subframe,(mini-)slot, and/or symbol boundary alignment according to timingrelationships across serving cells aggregated by carrier aggregation.This may not imply that base station transmissions start at thesubframe, (mini-) slot, and/or symbol boundary. Unlicensed celloperation (e.g., LAA and/or NR-U) may support transmitting PDSCH, forexample, when not all OFDM symbols are available for transmission in asubframe according to LBT. Delivery of necessary control information forthe PDSCH may also be supported.

An LBT procedure may be employed for fair and friendly coexistence of a3GPP system (e.g., LTE and/or NR) with other operators and technologiesoperating in unlicensed spectrum. For example, a node attempting totransmit on a carrier in unlicensed spectrum may perform a CCA as a partof an LBT procedure to determine if the channel is free for use. The LBTprocedure may involve energy detection to determine if the channel isbeing used. For example, regulatory requirements in some regions, e.g.,in Europe, specify an energy detection threshold such that if a nodereceives energy greater than the threshold, the node assumes that thechannel is being used and not free. While nodes may follow suchregulatory requirements, a node may optionally use a lower threshold forenergy detection than that specified by regulatory requirements. A radioaccess technology (e.g., LTE and/or NR) may employ a mechanism toadaptively change the energy detection threshold. For example, NR-U mayemploy a mechanism to adaptively lower the energy detection thresholdfrom an upper bound. An adaptation mechanism may not preclude static orsemi-static setting of the threshold. In an example Category 4 LBT (CAT4LBT) mechanism or other type of LBT mechanisms may be implemented.

Various example LBT mechanisms may be implemented. In an example, forsome signals, in some implementation scenarios, in some situations,and/or in some frequencies no LBT procedure may be performed by thetransmitting entity. In an example, Category 1 (CAT1, e.g., no LBT) maybe implemented in one or more cases. For example, a channel inunlicensed band may be hold by a first device (e.g., a base station forDL transmission), and a second device (e.g., a wireless device) takesover the for a transmission without performing the CAT1 LBT. In anexample, Category 2 (CAT2, e.g. LBT without random back-off and/orone-shot LBT) may be implemented. The duration of time determining thatthe channel is idle may be deterministic (e.g., by a regulation). A basestation may transmit an uplink grant indicating a type of LBT (e.g.,CAT2 LBT) to a wireless device. CAT1 LBT and CAT2 LBT may be employedfor Channel occupancy time (COT) sharing. For example, a base station (awireless device) may transmit an uplink grant (resp. uplink controlinformation) comprising a type of LBT. For example, CAT1 LBT and/or CAT2LBT in the uplink grant (or uplink control information) may indicate, toa receiving device (e.g., a base station, and/or a wireless device) totrigger COT sharing. In an example, Category 3 (CAT3, e.g. LBT withrandom back-off with a contention window of fixed size) may beimplemented. The LBT procedure may have the following procedure as oneof its components. The transmitting entity may draw a random number Nwithin a contention window. The size of the contention window may bespecified by the minimum and maximum value of N. The size of thecontention window may be fixed. The random number N may be employed inthe LBT procedure to determine the duration of time that the channel issensed to be idle before the transmitting entity transmits on thechannel. In an example, Category 4 (CAT4, e.g. LBT with random back-offwith a contention window of variable size) may be implemented. Thetransmitting entity may draw a random number N within a contentionwindow. The size of contention window may be specified by the minimumand maximum value of N. The transmitting entity may vary the size of thecontention window when drawing the random number N. The random number Nmay be used in the LBT procedure to determine the duration of time thatthe channel is sensed to be idle before the transmitting entitytransmits on the channel.

In an example, a wireless device may employ uplink (UL) LBT. The UL LBTmay be different from a downlink (DL) LBT (e.g. by using different LBTmechanisms or parameters) for example, since the NR-U UL may be based onscheduled access which affects a wireless device's channel contentionopportunities. Other considerations motivating a different UL LBTcomprise, but are not limited to, multiplexing of multiple wirelessdevices in a subframe (slot, and/or mini-slot).

In an example, DL transmission burst(s) may be a continuous (unicast,multicast, broadcast, and/or combination thereof) transmission by a basestation (e.g., to one or more wireless devices) on a carrier component(CC). UL transmission burst(s) may be a continuous transmission from oneor more wireless devices to a base station on a CC. In an example, DLtransmission burst(s) and UL transmission burst(s) on a CC in anunlicensed spectrum may be scheduled in a TDM manner over the sameunlicensed carrier. Switching between DL transmission burst(s) and ULtransmission burst(s) may require an LBT (e.g., CAT1 LBT, CAT2 LBT, CAT3LBT, and/or CAT4 LBT). For example, an instant in time may be part of aDL transmission burst or an UL transmission burst.

Channel occupancy time (COT) sharing may be employed in NR-U. COTsharing may be a mechanism by which one or more wireless devices share achannel that is sensed as idle by at least one of the one or morewireless devices. For example, one or more first devices may occupy achannel via an LBT (e.g., the channel is sensed as idle based on CAT4LBT) and one or more second devices may share the channel using an LBT(e.g., 25 us LBT) within a maximum COT (MCOT) limit. For example, theMCOT limit may be given per priority class, logical channel priority,and/or wireless device specific. COT sharing may allow a concession forUL in unlicensed band. For example, a base station may transmit anuplink grant to a wireless device for a UL transmission. For example, abase station may occupy a channel and transmit, to one or more wirelessdevices a control signal indicating that the one or more wirelessdevices may use the channel. For example, the control signal maycomprise an uplink grant and/or a particular LBT type (e.g., CAT1 LBTand/or CAT2 LBT). The one or more wireless device may determine COTsharing based at least on the uplink grant and/or the particular LBTtype. The wireless device may perform UL transmission(s) with dynamicgrant and/or configured grant (e.g., Type 1, Type2, autonomous UL) witha particular LBT (e.g., CAT2 LBT such as 25 us LBT) in the configuredperiod, for example, if a COT sharing is triggered. A COT sharing may betriggered by a wireless device. For example, a wireless deviceperforming UL transmission(s) based on a configured grant (e.g., Type 1,Type2, autonomous UL) may transmit an uplink control informationindicating the COT sharing (UL-DL switching within a (M)COT). A startingtime of DL transmission(s) in the COT sharing triggered by a wirelessdevice may be indicated in one or more ways. For example, one or moreparameters in the uplink control information indicate the starting time.For example, resource configuration(s) of configured grant(s)configured/activated by a base station may indicate the starting time.For example, a base station may be allowed to perform DL transmission(s)after or in response to UL transmission(s) on the configured grant(e.g., Type 1, Type 2, and/or autonomous UL). There may be a delay(e.g., at least 4 ms) between the uplink grant and the UL transmission.The delay may be predefined, semi-statically configured (via an RRCmessage) by a base station, and/or dynamically indicated (e.g., via anuplink grant) by a base station. The delay may not be accounted in theCOT duration.

In an example, single and multiple DL to UL and UL to DL switchingwithin a shared COT may be supported. Example LBT requirements tosupport single or multiple switching points, may comprise: for a gap ofless than 16 us: no-LBT may be used; for a gap of above 16 us but doesnot exceed 25 us: one-shot LBT may be used; for single switching point,for a gap from DL transmission to UL transmission exceeds 25 us:one-shot LBT may be used; for multiple switching points, for a gap fromDL transmission to UL transmission exceeds 25 us, one-shot LBT may beused.

In an example, a signal that facilitates its detection with lowcomplexity may be useful for wireless device power saving, improvedcoexistence, spatial reuse at least within the same operator network,serving cell transmission burst acquisition, etc. In an example, a radioaccess technology (e.g., LTE and/or NR) may employ a signal comprisingat least SS/PBCH block burst set transmission. Other channels andsignals may be transmitted together as part of the signal. In anexample, the signal may be a discovery reference signal (DRS). There maybe no gap within a time span that the signal is transmitted at leastwithin a beam. In an example, a gap may be defined for beam switching.In an example, a block-interlaced based PUSCH may be employed. In anexample, the same interlace structure for PUCCH and PUSCH may be used.In an example, interlaced based PRACH may be used.

In an example, initial active DL/UL BWP may be approximately 20 MHz fora first unlicensed band, e.g., in a 5 GHz unlicensed band. An initialactive DL/UL BWP in one or more unlicensed bands may be similar (e.g.,approximately 20 MHz in a 5 GHz and/or 6 GHz unlicensed spectrum), forexample, if similar channelization is used in the one or more unlicensedbands (e.g., by a regulation).

In an example, HARQ acknowledge and negative acknowledge (A/N) for thecorresponding data may be transmitted in a shared COT (e.g., with a CAT2LBT). In some examples, the HARQ A/N may be transmitted in a separateCOT (e.g., the separate COT may require a CAT4 LBT). In an example, whenUL HARQ feedback is transmitted on unlicensed band, a radio accesstechnology (e.g., LTE and/or NR) may support flexible triggering andmultiplexing of HARQ feedback for one or more DL HARQ processes. HARQprocess information may be defined independent of timing (e.g., timeand/or frequency resource) of transmission. In an example, UCI on PUSCHmay carry HARQ process ID, NDI, RVID. In an example, Downlink FeedbackInformation (DFI) may be used for transmission of HARQ feedback forconfigured grant.

In an example, CBRA and CFRA may be supported on SpCell. CFRA may besupported on SCells. In an example, an RAR may be transmitted viaSpCell, e.g., non-standalone scenario. In an example, an RAR may betransmitted via SpCell and/or SCell, e.g., standalone scenario. In anexample, a predefined HARQ process ID for an RAR.

In an example, carrier aggregation between licensed band NR (PCell) andNR-U (SCell) may be supported. In an example, NR-U SCell may have bothDL and UL, or DL-only. In an example, dual connectivity between licensedband LTE (PCell) and NR-U (PSCell) may be supported. In an example,Stand-alone NR-U where all carriers are in one or more unlicensed bandsmay be supported. In an example, an NR cell with DL in unlicensed bandand UL in licensed band or vice versa may be supported. In an example,dual connectivity between licensed band NR (PCell) and NR-U (PSCell) maybe supported.

In an example, a radio access technology (e.g., LTE and/or NR) operatingbandwidth may be an integer multiple of 20 MHz, for example, if absenceof Wi-Fi cannot be guaranteed (e.g. by regulation) in an unlicensed band(e.g., 5 GHz, 6 GHZ, and/or sub-7 GHz) where the radio access technology(e.g., LTE and/or NR) is operating. In an example, a wireless device mayperformance or more LBTs in units of 20 MHz. In an example, receiverassisted LBT (e.g., RTS/CTS type mechanism) and/or on-demand receiverassisted LBT (e.g., for example receiver assisted LBT enabled only whenneeded) may be employed. In an example, techniques to enhance spatialreuse may be used.

In an operation in an unlicensed band (e.g., LTE eLAA/feLAA and/orNR-U), a wireless device may measure (averaged) received signal strengthindicator (RSSI) and/or may determine a channel occupancy (CO) of one ormore channels. For example, the wireless device may report channeloccupancy and/or RSSI measurements to the base station. It may bebeneficial to report a metric to represent channel occupancy and/ormedium contention. The channel occupancy may be defined as a portion(e.g., percentage) of time that RSSI was measured above a configuredthreshold. The RSSI and the CO measurement reports may assist the basestation to detect the hidden node and/or to achieve a load balancedchannel access to reduce the channel access collisions.

Channel congestion may cause an LBT failure. The probability ofsuccessful LBT may be increased for random access and/or for datatransmission if, for example, the wireless device selects thecell/BWP/channel with the lowest channel congestion or load. Forexample, channel occupancy aware RACH procedure may be considered toreduce LBT failure. For example, the random access backoff time for thewireless device may be adjusted based on channel conditions (e.g., basedon channel occupancy and/or RSSI measurements). For example, a basestation may (semi-statically and/or dynamically) transmit a randomaccess backoff. For example, the random access backoff may bepredefined. For example, the random access backoff may be incrementedafter or in response to one or more random access response receptionfailures corresponding to one or more random access preamble attempts.

The carrier aggregation with at least one SCell operating in theunlicensed spectrum may be referred to as Licensed-Assisted Access(LAA). In LAA, the configured set of serving cells for a UE may includeat least one SCell operating in the unlicensed spectrum according to afirst frame structure (e.g., frame structure Type 3). The SCell may becalled LAA SCell.

In an example, if the absence of IEEE802.11n/11ac devices sharing thecarrier cannot be guaranteed on a long term basis (e.g., by level ofregulation), and for if the maximum number of unlicensed channels thatnetwork may simultaneously transmit on is equal to or less than 4, themaximum frequency separation between any two carrier center frequencieson which LAA SCell transmissions are performed may be less than or equalto 62 MHz. In an example, the UE may be required to support frequencyseparation.

In an example, base station and UE may apply Listen-Before-Talk (LBT)before performing a transmission on LAA SCell. When LBT is applied, thetransmitter may listen to/sense the channel to determine whether thechannel is free or busy. If the channel is determined to be free/clear,the transmitter may perform the transmission; otherwise, it may notperform the transmission. In an example, if base station uses channelaccess signals of other technologies for the purpose of channel access,it may continue to meet the LAA maximum energy detection thresholdrequirement.

In an example, the combined time of transmissions compliant with thechannel access procedure by a base station may not exceed 50 ms in anycontiguous 1 second period on an LAA SCell.

In an example, which LBT type (e.g., type 1 or type 2 uplink channelaccess) the UE applies may be signaled via uplink grant for uplink PUSCHtransmission on LAA SCells. In an example, for Autonomous Uplink (AUL)transmissions the LBT may not be signaled in the uplink grant.

In an example, for type 1 uplink channel access on AUL, base station maysignal the Channel Access Priority Class for a logical channel and UEmay select the highest Channel Access Priority Class (e.g., with a lowernumber in FIG. 16) of the logical channel(s) with MAC SDU multiplexedinto the MAC PDU. In an example, the MAC CEs except padding BSR may usethe lowest Channel Access Priority Class.

In an example, for type 2 uplink channel access on AUL, the UE mayselect logical channels corresponding to any Channel Access PriorityClass for UL transmission in the subframes signaled by base station incommon downlink control signaling.

In an example, for uplink LAA operation, the base station may notschedule the UE more subframes than the minimum necessary to transmitthe traffic corresponding to the selected Channel Access Priority Classor lower (e.g., with a lower number in FIG. 16), than the channel AccessPriority Class signaled in UL grant based on the latest BSR and receiveduplink traffic from the UE if type 1 uplink channel access procedure issignaled to the UE; and/or Channel Access Priority Class used by thebase station based on the downlink traffic, the latest BSR and receivedUL traffic from the UE if type 2 uplink channel access procedure issignaled to the UE.

In an example, a first number (e.g., four) Channel Access PriorityClasses may be used when performing uplink and downlink transmissions inLAA carriers. In an example in FIG. 16 shows which Channel AccessPriority Class may be used by traffic belonging to the differentstandardized QCIs. A non-standardized QCI (e.g., Operator specific QCI)may use suitable Channel Access Priority Class based on the FIG. 16 forexample, e.g., the Channel Access Priority Class used for anon-standardized QCI should be the Channel Access Priority Class of thestandardized QCIs which best matches the traffic class of thenon-standardized QCI.

In an example, for uplink, the base station may select the ChannelAccess Priority Class by taking into account the lowest priority QCI ina Logical Channel Group.

In an example, four Channel Access Priority Classes may be used. If a DLtransmission burst with PDSCH is transmitted, for which channel accesshas been obtained using Channel Access Priority Class P (1 . . . 4), thebase station may ensure the following where a DL transmission burstrefers to the continuous transmission by base station after a successfulLBT: the transmission duration of the DL transmission burst may notexceed the minimum duration needed to transmit all available bufferedtraffic corresponding to Channel Access Priority Class(es)≤P; thetransmission duration of the DL transmission burst may not exceed theMaximum Channel Occupancy Time for Channel Access Priority Class P; andadditional traffic corresponding to Channel Access Priority Class(s)>Pmay be included in the DL transmission burst once no more datacorresponding to Channel Access Priority Class≤P is available fortransmission. In such cases, base station may maximize occupancy of theremaining transmission resources in the DL transmission burst with thisadditional traffic.

In an example, when the PDCCH of an LAA SCell is configured, ifcross-carrier scheduling applies to uplink transmission, it may bescheduled for downlink transmission via its PDCCH and for uplinktransmission via the PDCCH of one other serving cell. In an example,when the PDCCH of an LAA SCell is configured, if self-scheduling appliesto both uplink transmission and downlink transmission, it may bescheduled for uplink transmission and downlink transmission via itsPDCCH.

In an example, Autonomous uplink may be supported on the SCells. In anexample, one or more autonomous uplink configuration may be supportedper SCell. In an example, multiple autonomous uplink configurations maybe active simultaneously when there is more than one SCell.

In an example, when autonomous uplink is configured by RRC, thefollowing information may be provided in an AUL configurationinformation element (e.g., AUL-Config): AUL C-RNTI; HARQ process IDsaul-harq-processes that may be configured for autonomous UL HARQoperation, the time period aul-retransmissionTimer before triggering anew transmission or a retransmission of the same HARQ process usingautonomous uplink; the bitmap aul-subframes that indicates the subframesthat are configured for autonomous UL HARQ operation.

In an example, when the autonomous uplink configuration is released byRRC, the corresponding configured grant may be cleared.

In an example, if AUL-Config is configured, the MAC entity may considerthat a configured uplink grant occurs in those subframes for whichaul-subframes is set to 1.

In an example, if AUL confirmation has been triggered and not cancelled,if the MAC entity has UL resources allocated for new transmission forthis TTI, the MAC entity may instruct a Multiplexing and Assemblyprocedure to generate an AUL confirmation MAC Control Element; the MACentity may cancel the triggered AUL confirmation.

In an example, the MAC entity may clear the configured uplink grant forthe SCell in response first transmission of AUL confirmation MAC ControlElement triggered by the AUL release for this SCell. In an example,retransmissions for uplink transmissions using autonomous uplink maycontinue after clearing the corresponding configured uplink grant.

In an example, a MAC entity may be configured with AUL-RNTI for AULoperation. In an example, an uplink grant may be received for atransmission time interval for a Serving Cell on the PDCCH for the MACentity's AUL C-RNTI. In an example, if the NDI in the received HARQinformation is 1, the MAC entity may consider the NDI for thecorresponding HARQ process not to have been toggled. The MAC entity maydeliver the uplink grant and the associated HARQ information to the HARQentity for this transmission time interval. In an example, if the NDI inthe received HARQ information is 0 and if PDCCH contents indicate AULrelease, the MAC entity may trigger an AUL confirmation. If an uplinkgrant for this TTI has been configured, the MAC entity may consider theNDI bit for the corresponding HARQ process to have been toggled. The MACentity may deliver the configured uplink grant and the associated HARQinformation to the HARQ entity for this TTI. In an example, if the NDIin the received HARQ information is 0 and if PDCCH contents indicate AULactivation, the MAC entity may trigger an AUL confirmation.

In an example, if the aul-retransmissionTimer is not running and ifthere is no uplink grant previously delivered to the HARQ entity for thesame HARQ process; or if the previous uplink grant delivered to the HARQentity for the same HARQ process was not an uplink grant received forthe MAC entity's C-RNTI; or if the HARQ_FEEDBACK is set to ACK for thecorresponding HARQ process, the MAC entity may deliver the configureduplink grant, and the associated HARQ information to the HARQ entity forthis TTI.

In an example, the NDI transmitted in the PDCCH for the MAC entity's AULC-RNTI may be set to 0.

In an example, for configured uplink grants, if UL HARQ operation isautonomous, the HARQ Process ID associated with a TTI for transmissionon a Serving Cell may be selected by the UE implementation from the HARQprocess IDs that are configured for autonomous UL HARQ operation byupper layers for example, in aul-harq-processes.

In an example, for autonomous HARQ, a HARQ process may maintain a statevariable e.g., HARQ_FEEDBACK, which may indicate the HARQ feedback forthe MAC PDU currently in the buffer, and/or a timeraul-retransmissionTimer which may prohibit new transmission orretransmission for the same HARQ process when the timer is running.

In an example, when the HARQ feedback is received for a TB, the HARQprocess may set HARQ_FEEDBACK to the received value; and may stop theaul-retransmissionTimer if running.

In an example, when PUSCH transmission is performed for a TB and if theuplink grant is a configured grant for the MAC entity's AUL C-RNTI, theHARQ process start the aul-retransmissionTimer.

In an example, if the HARQ entity requests a new transmission, the HARQprocess may set HARQ_FEEDBACK to NACK if UL HARQ operation is autonomousasynchronous. if the uplink grant was addressed to the AUL C-RNTI, setCURRENT_IRV to 0.

In an example, if aperiodic CSI requested for a TTI, the MAC entity maynot generate a MAC PDU for the HARQ entity in case the grant indicatedto the HARQ entity is a configured uplink grant activated by the MACentity's AUL C-RNTI.

In an example, if the UE detects on the scheduling cell for ULtransmissions on an LAA SCell a transmission of DCI (e.g., Format 0A/4A)with the CRC scrambled by AUL C-RNTI carrying AUL-DFI, the UE may usethe autonomous uplink feedback information according to the followingprocedures: for a HARQ process configured for autonomous uplinktransmission, the corresponding HARQ-ACK feedback may be delivered tohigher layers. For the HARQ processes not configured for autonomousuplink transmission, the corresponding HARQ-ACK feedback may notdelivered to higher layers; for an uplink transmission insubframe/slot/TTI n, the UE may expect HARQ-ACK feedback in the AUL-DFIat earliest in subframe n+4; If the UE receives AUL-DFI in a subframeindicating ACK for a HARQ process, the UE may not be expected to receiveAUL-DFI indicating ACK for the same HARQ process prior to 4 ms after theUE transmits another uplink transmission associated with that HARQprocess;

In an example, a UE may validate an autonomous uplink assignmentPDCCH/EPDCCH if all the following conditions are met: the CRC paritybits obtained for the PDCCH/EPDCCH payload are scrambled with the AULC-RNTI; and the ‘Flag for AUL differentiation’ indicatesactivating/releasing AUL transmission. In an example, one or more fieldsin an activation DCI may be pre-configured values for validation.

In an example, a base station may configure consecutive configured grantresources in time. There may be no gaps between the consecutiveconfigured grant resources. In an example, the base station mayconfigure non-consecutive configured grant resources. In an example, thenon-consecutive configured grant resources may have a periodicity. In anexample, the non-consecutive configured grant resources may benon-periodic. In an example, a first pattern of configured grantresources may be repeated in time wherein the resources of the firstconfigured resources are non-periodic.

In an example, a wireless device may select an HARQ process ID from anRRC configured set of HARQ IDs for transmission of packet via aconfigured grant resource on an unlicensed cell.

In an example, a downlink control information may comprise downlinkfeedback information (DFI), wherein the DFI includes pending HARQ ACKfeedback for prior configured grant transmissions from the same UE. Inan example, DFI may include HARQ feedback for dynamically scheduled ULtransmissions using HARQ IDs configured for NR-unlicensed configuredgrant transmission.

In an example, a packet/transport block corresponding to a HARQ processthat was initially transmitted via a configured grant resource may beretransmitted via a configured grant resource. In an example, apacket/transport block corresponding to a HARQ process that wasinitially transmitted via a configured grant resource may beretransmitted via resources dynamically scheduled by an UL grant. In anexample, a wireless device may autonomously initiate retransmission fora HARQ process that was initially transmitted via configured grantmechanism for NR-unlicensed when a NACK is received (e.g., via DFI) forthe corresponding HARQ process. In an example, a wireless device mayautonomously initiate retransmission for a HARQ process that wasinitially transmitted via configured grant mechanism for NR-unlicensedwhen no feedback is received gNB before a timer is expired.

In an example, a block-interlaced based PUSCH may be employed. In anexample, the same interlace structure for PUCCH and PUSCH may be used.In an example, interlaced based PRACH may be used.

In an example, initial active DL/UL BWP may be approximately 20 MHz for5 GHz band. In an example, initial active DL/UL BWP may be approximately20 MHz for 6 GHz band if similar channelization as 5 GHz band is usedfor 6 GHz band.

In an example, HARQ A/N for the corresponding data may be transmitted inthe same shared COT. In some examples, the HARQ A/N may be transmittedin a separate COT from the one the corresponding data was transmitted.

In an example, when UL HARQ feedback is transmitted on unlicensed band,NR-U may consider mechanisms to support flexible triggering andmultiplexing of HARQ feedback for one or more DL HARQ processes.

In an example, the dependencies of HARQ process information to thetiming may be removed. In an example, UCI on PUSCH may carry HARQprocess ID, NDI, RVID. In an example, Downlink Feedback Information(DFI) may be used for transmission of HARQ feedback for configuredgrant.

In an example, both CBRA and CFRA may be supported on NR-U SpCell andCFRA may be supported on NR-U SCells. In an example, RAR may betransmitted via SpCell. In an example, a predefined HARQ process ID forRAR.

In an example, carrier aggregation between licensed band NR (PCell) andNR-U (SCell) may be supported. In an example, NR-U SCell may have bothDL and UL, or DL-only. In an example, dual connectivity between licensedband LTE (PCell) and NR-U (PSCell) may be supported. In an example,Stand-alone NR-U where all carriers are in unlicensed spectrum may besupported. In an example, an NR cell with DL in unlicensed band and ULin licensed band may be supported. In an example, dual connectivitybetween licensed band NR (PCell) and NR-U (PSCell) may be supported.

In an example, if absence of Wi-Fi cannot be guaranteed (e.g. byregulation) in a band (e.g., sub-7 GHz) where NR-U is operating, theNR-U operating bandwidth may be an integer multiple of 20 MHz. In anexample, at least for band where absence of Wi-Fi cannot be guaranteed(e.g. by regulation), LBT can be performed in units of 20 MHz, alsoknown as subbands. In an example, receiver assisted LBT (e.g., RTS/CTStype mechanism) and/or on-demand receiver assisted LBT (e.g., forexample receiver assisted LBT enabled only when needed) may be employed.In an example, techniques to enhance spatial reuse may be used. In anexample, preamble detection may be used.

In an example, with scheduled PUSCH transmissions on an unlicensedcarrier, the network first needs to gain access to the channel totransmit PDCCH and then the UE needs to perform LBT again prior totransmitting on the resource. Such procedure tends to increase latencyespecially when the channel is loaded. In an example, a mechanism ofautonomous uplink transmission may be used. In an example, a UE may bepre-allocated a resource for transmission similar to UL SPS and performsLBT prior to using the resource. In an example, autonomous uplink may bebased on the Configured Grant functionality (e.g., Type 1 and/or Type2).

In an example, the HARQ process identity may be transmitted by the UE(e.g., as UCI). This may enable a UE to use the first availabletransmission opportunity irrespective of the HARQ process. In anexample, UCI on PUSCH may be used to carry HARQ process ID, NDI andRVID.

For unlicensed band, UL dynamic grant scheduled transmission mayincrease the delay and transmission failure possibility due to at leasttwo LBTs of UE and gNB. Pre-configured grant such as configured grant inNR may be used for NR-U, which may decrease the number of LBTs performedand control signaling overhead.

In an example, in a Type 1 configured grant, an uplink grant is providedby RRC, and stored as configured uplink grant. In an example, in Type 2configured grant, an uplink grant is provided by PDCCH, and stored orcleared as configured uplink grant based on L1 signaling indicatingconfigured grant activation or deactivation.

In an example, there may not be a dependency between HARQ processinformation to the timing. In an example, UCI on PUSCH may carry HARQprocess ID, NDI, RVID, etc. In an example, UE may autonomously selectone HARQ process ID which is informed to gNB by UCI.

In an example, a UE may perform non-adaptive retransmission with theconfigured uplink grant. When dynamic grant for configured grantretransmission is blocked due to LBT, UE may try to transmit in the nextavailable resource with configured grant.

In an example, Downlink Feedback Information (DFI) may be transmitted(e.g., using DCI) may include HARQ feedback for configured granttransmission. The UE may perform transmission/retransmission usingconfigured grant according to DFI including HARQ feedback. In anexample, wideband carrier with more than one channels is supported onNR-based unlicensed cell.

In an example, UE multiplexing and collision avoidance mechanismsbetween configured grant transmissions and between configured grant andscheduled grant transmissions may be used.

In an implementation, NR-unlicensed configured grant transmission maynot be allowed during the time when it overlaps with occasionsconfigured for potential NR-U DRS of the serving cell.

In an example, an RRC configured bitmap may be used to the allowed timeresource for configured grant transmission on subframe/slot/symbollevel. For example, in FeLAA, an RRC configured bitmap of 40 bits may beused. Such a mechanism may provide flexibility to assign or excludecertain subframes/slots/symbols for configured UL.

In an example, RRC signaling may indicate (e.g., for Type 1 configuredgrants) the time domain resource allocation e.g., periodicity, offset inthe frame, start symbol and length of PUSCH and K-repetition of theconfigured grant resource. In an example for Type 2 configured grant,RRC may indicate periodicity and K-repetition in time domain. The othertime domain related parameters may be given through DCI activationscrambled with a corresponding RNTI for configured grants (e.g.,CS-RNTI). In an example, some enhancements may be used in differentapplication scenario such as URLLC. For example, the granularity of timedomain allocation may be based on slot instead of OFDM symbol. In anexample, the K-repetition may be reinterpreted as number of configuredresource within a period. In an example, UE may start configured granttransmission from any configured resource boundary and occupy any numberof the configured resource.

In an example, resource allocation in NR-U may be based on frequencyinterlaces. In an example, to comply with the regulatory requirements inthe unlicensed spectrum such as the minimum OCB and maximum PSDrequirements, the resource configuration may include the frequencyinterlace(s) to be used within the configured frequency resources.

In an example, a wireless device may be configured with a widebandcarrier and/or a wideband UL BWP that spans multiple subbands. In anexample a subband may be a 20 MHz unlicensed channel. In order toincrease the resiliency to LBT failure, a wireless device may beconfigured with a frequency-domain resource, e.g., one or more frequencyinterlaces, across multiple subbands. In an example, a wireless devicemay perform multiple subband LBT procedures. Based on the results of thesubband LBT procedures, the wireless device may transmit on one or moresubbands for which the LBT procedure(s) are successful. In an example,the wireless device may select the number of subbands to use based onthe traffic type or the TB size.

In an example, for the uplink transmission with configured grant inNR-U, configuration of frequency-domain resources may include one ormore frequency interlaces. In an example, frequency-domain resources maybe configured across multiple subbands of a wideband UL BWP configuredto the UE for transmission with configured grant in NR-U.

In an example, a wireless device operating in unlicensed bands may betransmitting uplink packets from different traffic classes (e.g., QCIs)with different latency and/or bit rate requirements for which a singleresource configuration, e.g., periodicity and TBS, may not be adequate.In an example, a wireless device may be configured with multiple activeUL configured grants in a BWP of a cell. A wireless device may beconfigured with multiple resource configurations per UE for the uplinktransmission with configured grant to satisfy the diverse QoSrequirements anticipated in NR-U.

In an example, to improve the resource utilization with pre-configuredresources one or more wireless devices may be configured with sametime-domain resources, and either orthogonal or same frequencyinterlaces on the same unlicensed channel. In an example, thetransmission starting points of the one or more wireless devices may bealigned to avoid mutual blocking during the LBT. In an example, if acollision occurs, the receiving base station may identify the UEs usingother pre-configured resources, such as DMRS, and resolve the collisionin the spatial or code domains.

Due to the uncertainty of the unlicensed channel availability in NR-U, aUE with data ready to transmit may not gain access to the pre-configuredresources as a result of LBT failure. The missing of the pre-configuredtransmission opportunity may lead to underutilized resources and/orexcessive latencies. In an example, the wireless device that missed apre-configured periodic transmission opportunity may defer its channelaccess for the remaining time span of the configured period until thefollowing transmission opportunity.

In an example, a wireless device may be configured with multipletransmission occasions over the pre-configured time-domain resourcewithin a CG period. In an example, before the beginning of thepre-configured period, the wireless device may perform the LBT proceduretowards accessing the first transmission occasion/burst startingposition. If the LBT is successful, the UE may start transmitting one ormore PUSCHs up to the end of the CG resource within the pre-configuredperiod. In an example, if the LBT fails, the UE may not defer thechannel access for the remaining period. The wireless device may resumeits channel access attempt by performing LBT towards accessing thesecond transmission occasion, and so on.

In an example, a base station may dynamically allow a group of wirelessdevices to transmit on additional resources in accordance with aconfigured grant (for example except for periodicity and time offset) bysending a DL common alignment signal such as a DCI. In an example, theDCI may be scrambled by a group ID.

In an example, transmission start time of multiple UEs configured withthe same time-domain resources and either same or orthogonal frequencyinterlaces on a given unlicensed channel may be aligned. In an example,base station may align uplink transmission with configured grant usingan Alignment Signal (e.g., a group common DCI).

In an example, a retransmission may be scheduled with an uplink grantfor a HARQ process that was initially transmitted with configured grant.

In an example, UCI multiplexed with data and transmitted via PUSCH maycarry HARQ process ID, NDI, RVID and other information related to thetransmitted data. UCI multiplexed with data and carrying informationrelated to data may need to be encoded and decoded separately before thedata to enable the soft combining of the packet at the base station.

In an example, the HARQ process ID may be determined based on thefrequency interlace and/or the DMRS cyclic shift (such that initial andretransmission of a UE TB may be identified).

In an example, the base station may provide pending HARQ feedback forone or more PUSCH transmitted with configured grant within previous ULbursts using a GC-DCI scrambled with a group RNTI.

In an example, a base station may perform a CAT4 LBT and acquire anMCOT. The base station may transmit a DL Alignment signal to trigger atransmission from one or more UEs based on the configured grant. The UEswith data to transmit may share the base station acquired MCOT andeither access the channel immediately, if the PUSCH transmission canstart after gap that is less than 16 pec or using CAT2 LBT otherwise. Insuch case, the UEs transmitting in response to the DL Alignment signallimit their COT by the gNB-acquired MCOT.

In an example, the base station may provide HARQ feedback for one ormore PUSCH transmitted with CG within the UE-acquired MCOT in either aGC-DCI or frequency multiplexed UE-specific DCIs. The base station shareone or more UE-acquired MCOT(s) and access the channel with CAT2 LBT.

In an example, a wireless device may update its configured-granttransmission parameters such as MCS, RI and PMI, and indicate thechanges to the base station within the uplink burst. In an example, apre-configured pool of pilot signals may indicate the change, e.g., DMRSand cyclic shifts. In an example, UCI multiplexed with PUSCH mayindicate the UE updated transmission parameters.

In an example, the base station may update the configured granttransmission parameters, e.g., based on received signal quality such asSINR or BLER, and indicate the new parameters in a DCI. In an example,the base station may use a GC-DCI. In an example, a UE-specific DCI maybe used.

In an example, multiple candidate transmission occasions within a periodmay be configured. In an example, the candidate transmission occasionswithin a period can be configured by network or derived by UE accordingto the configuration. In an example, for NR-U UL configured grant, awireless device may determine multiple candidate transmission occasionswithin a period. In an example, the multiple transmission occasions maybe based on the first candidate transmission occasion, duration of PUSCHand period P.

In an example, a wireless device may perform multiple LBTs when it isconfigured with a BWP with frequency bandwidth larger than 20 MHz for ULconfigured grant transmission. In an example, if a subband is sensed tobe busy, UE may not transmit an UL signal in the active BWP on theunlicensed spectrum. In an example, UE may transmit the UL signal unlessall the subbands of the frequency bandwidth are sensed to be idle.

In an example, a wireless device may have multiple frequency resourceallocations per BWP. In an example, a UE may be configured with multipleconfigured grant resource configurations in a BWP by RRC. Multipleconfigured grant configurations may be activated and differentconfigured grant configurations may have different combinations ofsubbands. In an example, a configuration may be indexed, and the indexmay be carried by the activation/deactivation DCI to indicate the targetconfiguration. In an example, for NR-U UL configured grant, multipleresource configurations may be supported per BWP. Different resourceconfigurations may correspond to different subband combinations.

In an example, for a HARQ process that was initially transmitted viaconfigured grant resource, retransmission may be via a configured grantresource or resource scheduled by UL grant.

In an example, NR-U UCI for configured grant may be mapped to the REsafter the symbols carrying DMRS in PUSCH on the allocated subbands. Inan example, UCI may be mapped from the symbol of the PUSCH before whichthe channel is sensed to be idle.

In an example, for NR-U UL configured grant, UCI may be mapped on theresource of the actual transmission occasion. In an example, NR-U UCIfor configured grant is mapped to the REs after the symbols carryingDMRS in the transmitted PUSCH.

In an example, multiple UEs in NR unlicensed spectrum may be configuredwith configured grant resources with aligned starting timing in timedomain. The UEs may perform LBT simultaneously when there are packets intheir buffers before the transmission occasion of configured grantresource. In an example, each UE may sense the channel is idle and maystart PUSCH transmission. This would lead to collision of ULtransmissions among multiple UEs.

In an example, DMRS may be used for UE identification since DMRSconfiguration(s)/parameter(s) are UE-specifically configured. In anexample, when collision happens, base station may identify colliding UEsvia DMRS detection. If multiple UEs transmit UL data simultaneouslyusing the same starting position in time domain, base station mayidentify the UEs transmitting UL data via DMRS detection. In an example,base station may schedule retransmission or feedback NACK for thecorresponding UE.

For NR grant-free uplink (GUL) transmission in unlicensed band, due tothe uncertainty of channel availability, a UE may beconfigured/scheduled with multiple transmission opportunities intime/frequency domain.

In an example in time domain, a UE can be configured with multipleconsecutive transmission occasions within a periodic window for GULtransmission. The UE may perform multiple LBT attempts until itsucceeds. To enable more LBT attempts at a finer channel accessgranularity for the UE, the UE may be configured with mini-slot leveltime domain resources for the periodic window. The consecutive timedomain resources for the periodic window may be configured througheither a bitmap or a tuple of parameters including start position,temporal length, and periodicity. In an example, a bitmap may be used toindicate slots/symbols/subframes that are configured with configuredgrant within a time duration. The bitmap may indicate a pattern and thepattern may be repeated for consecutive time durations.

In an example in NR-U, a UE with capability of subband LBT may beconfigured to operate multiple 20 MHz unlicensed channels. The basestation may configure a set of candidate resources distributed acrossthe multiple unlicensed channels for GUL transmission. The UE mayperform subband LBTs for each unlicensed channel. The UE may select theavailable candidate resource(s) to transmit the data. These candidateresources may be shared with multiple UEs by managing the transmissionstarting positions to avoid the inefficient resource utilization. In anexample, the base station may blindly detect the actual transmission(s)on the configured multiple candidate resources. In an example, a UE maybe configured with multiple candidate resources across multipleunlicensed channels for grant-free UL transmission, and the UE maytransmit data on one or more candidate resources based on subband LBTresults.

In an example, for NR-U configured grant, downlink signals and/orchannels such as PDCCH/PDSCH may be shared in a UE-initiated COT.

In an example, configured grant UCI (CG-UCI) on GUL transmission maycarry HARQ process ID, NDI, RVID, etc. and may remove the timingdependency of HARQ process. In an example, a UE may select the HARQprocess ID from an RRC configured set of HARQ process IDs. In anexample, if the configured resource(s) for GUL transmission is sharedwith multiple UEs, the CG-UCI may comprise the UE ID.

In an example, to support UE-initiated COT sharing for PDCCH and/orPDSCH transmission, the CG-UCI may carry COT sharing information. In anexample, besides HARQ related information, CG-UCI may include at leastUE ID, COT-sharing related information, CSI report for DL transmissionin a same UE-initiated COT, etc.

In an example, Downlink Feedback Information (DFI) may be transmittedvia a downlink control information (DCI) and may include HARQ feedbackfor configured grant transmission. In an example, time domain resourceallocation for the configured grant transmissions may provideflexibility.

In an example, a base station may configure a UE with a periodicity andrepetition times by RRC. In an example, repetition times may beconsidered as pre-configured transmission occasions within theperiodicity. The UE may transmit PUSCH after a successful LBT before anyof the candidate transmission opportunities scheduled by the configuredgrant, and gNB can perform blind detection on uplink data according tothe configuration.

In an example, in order to increase UL transmission opportunities,multiple frequency domain opportunities may be considered for NR-U.Multiple BWPs may be configured to UE. In an example, when data isavailable for transmission, the UE may attempt to perform LBT inmultiple BWPs according to the resource configuration for configuredgrant. If any LBT on these BWPs succeeds, the UE may transmit on eithermultiple BWPs or a selected one.

In an example, transmission at the configured grants may be code blockgroup (CBG) based. In an example, the HARQ feedback information in DFIor UCI may be considered CBG based. For example, DFI may provide CBGlevel HARQ feedback (e.g., ACK/NACK information per CBG of a TB). Forexample, UCI may indicate the CBGs of the TB that are transmitted via aconfigured grant resource. The UE may select the configured grant UL CBGand the transmitted CBGs information may be carried in the UCI. Or theDFI may provide CBG level feedback indication while UE can retransmitthe failed CBGs based on the DFI indication.

In an example, UE initiated MCOT sharing between configured grant UL andDL may be used in NR-U. In an example, a UE performing grant-freetransmission indicates in the grant-free UCI at least the followinginformation: HARQ process ID, UE-ID, NDI, PUSCH duration and COT sharinginformation. In an example, the grant-free UCI is scrambled with acell-specific RNTI. In an example, COT acquired by a UE may be sharedfor configured grant transmission.

In an example, DFI may carry HARQ feedback for configured granttransmission. HARQ-ACK information corresponding to HARQ processes atleast configured for CGU (configured grant for NR-U) may be includedalso in CGU-DFI.

In an example, a UE may transmit the UCI corresponding to a PUSCHtransmission via a configured grant resource via the PUSCH and the UCImay comprise at least HARQ process ID, NDI, RVID, etc. In an example,the mapping position of UCI may be from the second symbol to the secondlast symbol to minimize the effect of multiple starting/ending symbolpositions of PUSCH. If the PUSCH for configured grant has multiplestarting/ending positions, UCI mapping may avoid puncturing due to theLBT failure. In an example, the position of DM-RS for the PUSCH may beconsidered in the UCI mapping. In an example, the UCI can be mappedclose to DM-RS symbol to guarantee its reliability. In an example, UCImapping on PUSCH may consider multiple starting/ending positions and theposition of DM-RS for PUSCH and multiplexing with NR-UCI (e.g.,HARQ-ACK, CSI part 1, and CSI part 2).

In an example, the time-domain resource allocation for configured grantmay be given by the combination of offset value from SFN=0 andsymbol-level periodicity. To increase flexibility for time-domainresource allocation, the time-domain resource may be allocated using abitmap for a fixed period time. In an example, various numerologies forbitmap based time domain resource allocation may be considered. Forexample, the bitmap with fixed size may be interpreted as a scalablemanner with respect to numerology (e.g., one slot allocation for eachbit in case of 15 kHz SCS and two slot allocation for each bit in caseof 30 kHz SCS), or different bitmap size can be configured for each SCS(e.g., 40-bit bitmap for 15 kHz SCS and 80-bit bitmap for 30 kHz SCS).

In an example, a wireless device or base station may employ CBG basedtransmission. A UE may provide HARQ-ACK feedback for each CBG and basestation may retransmit the NACKed CBGs rather than the whole TB. TheCBG-based transmission may be useful for large TB scenario andespecially when some CBGs are punctured by URLLC or time-selectiveinterference.

In an example, CBG-based transmission may be realized by CBGTI (CBGtransmission indication) in scheduling DCI, for a retransmission of aTB, the bit value ‘0’ means that the corresponding CB G is nottransmitted/not to be transmitted and ‘1’ indicates that it istransmitted/to be transmitted for DL/UL.

In an example in NR-U, CBG based transmission may be used forPDSCH/PUSCH. In an example, CBG-based transmission may be used for PUSCHtransmission via configured grant resources. In an example, some symbolsmay not be transmitted due to LBT failure (e.g., puncturing) if multiplestarting positions for CGU PUSCH are allowed in NR-U. In an example, theUE may retransmit CBG(s) only belonging to the not-transmitted symbols.In order to support efficient CBG based transmission for CGU, we mayneed to consider how to configure control information (e.g., DFI, UCI).For example, CBGTI bits in the UCI may be included for UE to inform thebase station which CBGs are/were transmitted. In an example, CBG-levelHARQ feedback via DFI may be adopted for UE to retransmit the NACKedCBGs based on the DFI. In an example, if CBG-level HARQ-ACK feedback byDFI is adopted, it is necessary to devise the way to reduce thesignaling overhead (e.g., CBG-level HARQ-ACK for a limited number ofHARQ process IDs or TB-level HARQ-ACK for granted UL transmission).

In an example, a base station may indicate which slots configured grantUL transmission are allowed using a bitmap, comprising a plurality ofbits, via RRC signaling

In an example, to improve the efficiency of configured granttransmission in NR-U, one potential enhancement is defining a periodictransmission window instead of only one periodic transmission occasion.

In an example, configured grant UL transmission may be allowed withinthe gNB acquired COT. In an example, the collisions between configuredgrant UL transmission and scheduled transmission may be managed by thetransmission starting positions. In an example, UE-selected startingoffset and RRC configured starting offset may be used to coordinate UEmultiplexing for NR-U configured grant operation.

In an example, a timer may be used for autonomous configured grantretransmission for NR-U. The timer may be RRC configured with e.g. aslot granularity.

In an example, CBG operation for configured grant may overcome burstyinterference. With CBG based operation, the retransmission efficiencymay be increased. In an example, a UE may start configured grant ULtransmission after successful LBT. Some symbols or partial symbol may bediscarded based on when the UE finishes the LBT. In case the gNBreceived the rest of the CBGs correctly, the UE may need to retransmitCBG(s) belonging to the not-transmitted symbols instead of the full TB.

In an example, a HARQ process corresponding to a configured grant maynot have a dependency to the timing of the configured grant. In anexample, UCI on PUSCH may carry HARQ process ID, NDI, RVID, etc. In anexample, downlink feedback information (DFI) may be transmitted viadownlink control signaling. The DFI may comprise HARQ feedback forconfigured grant transmission. In an example, time domain resourceallocation of configured grant transmissions may have flexibility. In anexample, a retransmission may be based on a configured grant resource.

In an example, Type 1 and Type 2 configured grant mechanism may be usedfor operation of NR in unlicensed spectrum.

In an example, consecutive configured grant resources in time withoutany gaps in between the resources may be configured. In an example,non-consecutive configured grant resources (periodic or non-periodic)with gaps in between the resources may be configured.

In an example, a wireless device may select a HARQ process ID from anRRC configured set of HARQ IDs for NR-unlicensed configured granttransmission.

In an example, DFI may include pending HARQ ACK feedback for priorconfigured grant transmissions from the same wireless device. In anexample, DFI may include HARQ ACK feedback for scheduled ULtransmissions using HARQ IDs configured for NR-unlicensed configuredgrant transmission.

In an example, a HARQ process may be initially transmitted viaconfigured grant resource. The retransmission of the HARQ process may bevia a configured grant resource. In an example, a HARQ process that wasinitially transmitted via configured grant resource may be retransmittedvia resource scheduled by UL grant.

In an example, a wireless device may autonomously initiateretransmission for a HARQ process that was initially transmitted viaconfigured grant mechanism for NR-unlicensed, for example when one ormore of the following conditions is met: reception of NACK feedback viaDFI for the corresponding HARQ process, no reception of feedback fromgNB upon a timer expiration, etc.

In an example, NR-unlicensed configured grant transmission may not beallowed during the time when it overlaps with occasions configured forpotential NR-U DRS of the serving cell irrespective of the configuredtime domain resource for configured grant transmission.

In an example, to provide flexibility on time domain resource allocationof configured grants, a bitmap-based approach and configured parameterscomprising, for example, periodicity, offset in the frame, start symbol,length of PUSCH and K-repetition signaling, etc. may be used.

In an example, CBG based retransmissions for configured grant basedtransmissions may be used. CBG related control information may betransmitted as part of DFI and UCI

In an example, collision between configured grant and scheduled grantbased transmission may be avoided by management of starting point of thetransmission for configured grant and scheduled grant basedtransmission.

In an example, the resources utilized by the UCI, and multiplexing ofUCI and data information of PUSCH require consideration of DMRSplacement and starting and ending symbols of the configured grant basedtransmissions.

In an example, UCI corresponding to a configured grant transmission maycomprise UE-ID, COT sharing information, PUSCH duration, etc.

In an example, it may be problematic for the UE to assume ACK in absenceof reception of feedback, which may include explicit feedback orfeedback in the form of uplink grants. In an example, assuming NACK upona timer expiration may be a candidate solution to avoid LBT impact onreception of feedback.

In an example, sharing resources with gNB within COT(s) that is acquiredby UE(s) as part of configured grant based transmissions may besupported. In an example, allowing configured grant based transmissionswithin a gNB acquired COT may be supported

In an example, there may be one active BWP in a carrier. In an example,a BWP with multiple channels/subbands may be activated. In an example,when absence of Wi-Fi cannot be guaranteed (e.g. by regulation), LBT maybe performed in units of 20 MHz (subbands). In this case, there may bemultiple parallel LBT procedures for this BWP. The actual transmissionbandwidth may be subject to subband with LBT success, which may resultin dynamic bandwidth transmission within this active wideband BWP.

In an example, multiple active BWPs may be supported. To maximize theBWP utilization efficiency, the BWP bandwidth may be the same as thebandwidth of subband for LBT, e.g., LBT is carried out on each BWP. Thenetwork may activate/deactivate the BWPs based on data volume to betransmitted.

In an example, multiple non overlapped BWPs may be activated for a UEwithin a wide component carrier, which may be similar as carrieraggregation in LTE LAA. To maximize the BWP utilization efficiency, theBWP bandwidth may be the same as the bandwidth of subband for LBT, i.e.LBT is carrier out on each BWP. When more than one subband LBT success,it requires UE to have the capability to support multiple narrow RF or awide RF which includes these multiple activated BWPs.

In an example, a single wideband BWP may be activated for a UE within acomponent carrier. The bandwidth of wideband BWP may be in the unit ofsubband for LBT. For example, if the subband for LBT is 20 MHz in 5 GHzband, the wideband BWP bandwidth may consist of multiple 20 MHz. Theactual transmission bandwidth may be subject to subband with LBTsuccess, which may result in dynamic bandwidth transmission within thisactive wideband BWP.

In an example, active BWP switching may be achieved by use of schedulingDCI. In an example, the network may indicate to the UE a new active BWPto use for an upcoming, and any subsequent, data transmission/reception.In an example, a UE may monitor multiple, configured BWPs to determinewhich has been acquired for DL transmissions by the gNB. For example, aUE may be configured with monitoring occasion periodicity and offset foreach configured BWP. The UE may attempt to determine if a BWP has beenacquired by the gNB during those monitoring occasions. In an example,upon successfully determining that the channel is acquired, the UE maycontinue with that BWP as its active BWP, at least until indicatedotherwise or MCOT has been reached. In an example, when a UE hasdetermined that a BWP is active, it may attempt blind detection of PDCCHin configured CORESETs and it might also perform measurements onaperiodic or SPS resources.

In an example, for UL transmissions, a UE may be configured withmultiple UL resources, possibly in different BWPs and/or subbands. TheUE may have multiple LBT configurations, each tied to a BWP and/orsubband and possibly a beam pair link. The UE may be granted ULresources tied to one or more LBT configurations. Similarly, the UE maybe provided with multiple AUL/grant-free resources each requiring theuse of different LBT configurations. Providing a UE with multiple AULresources over multiple BWPs/subbands may ensure that if LBT fails usinga first LBT configuration for one AUL resource in one BWP/subband a UEcan attempt transmission in another AUL resource in another BWP/subband.This may reduce the channel access latency and make better use of theover-all unlicensed carrier.

In an example, multiple UE starting time offsets with sub-symbolgranularity may be supported for configured grant based transmissions.The UE may start transmissions accessing transmission opportunitiesprovided by a configured grant at the configured/indicated startingpositions.

For configured grant time domain resource allocation, a number ofallocated slots following the time instance corresponding to theindicated offset may be configured. In an example, multiple PUSCHs maybe configured/allocated within a slot.

The DFI for NR-unlicensed configured grants may include at least TBlevel HARQ-ACK bitmap for all UL HARQ processes. The DFI forNR-unlicensed configured grants may support RRC configured minimumduration, e.g., D, from the ending symbol pf the PUSCH to the startingsymbol of the DFI carrying HARQ-ACK for that PUSCH. UE may assume thatHARQ-ACK is valid only for PUSCH transmission ending before n-D, where nis the time corresponding to the beginning of the start symbol of theDFI. A UE blind decoding complexity may not be increased due to DFIsize. A size of DFI may be same as an existing DCI sizes in NR. The DFImay at least comprise: an NDI bit for each HARQ ID; HARQ-ACK bitmap forall UL HARQ processes for NR-U configured grant; and HARQ-ACK forscheduled PUSCH.

A configured grant UCI (CG-UCI) may be included in every configuredgrant PUSCH (CG-PUSCH) transmission.

A number of separately encoded UCIs multiplexed in a PUSCH transmittedusing a configured grant may be at most three.

A CG-UCI may comprise: HARQ ID; NDI; RV; COT sharing information, e.g.,LBT type/priority class, COT duration; UE-ID; CRC; indication of PUSCHstart/end point/slot; resource configuration index; multiple blankedOFDM symbols; transmission parameters, e.g., MCS, PMI, RI, SRI; sharedCG-UCI corresponding to multiple PUSCHs; SR information to indicate therequest of continuous PUSCH scheduling; UAI (similar to DAI in DL); ULtransmit power; CBG level ACK-NACK; CBGTI; etc.

Configuring dedicated time/frequency resource to each UE may increase alikelihood of resource waste and decreased user capacity. For example,burst traffic may result in the pre-configured dedicated resources to beunderutilized. For example, a UE with data ready to transmit may notgain access to the pre-configured resources as a result of LBT failure.For example, a network may improve the resource utilization withpre-configured resources by configuring a selected set of UEs, e.g., twoor more UEs, with same time-domain resources, and either orthogonal orsame frequency interlaces on the same LBT subband. For example, thenetwork may align the UEs transmission starting points to avoid mutualblocking during the LBT.

NR/NR-U may support the configuration of multiple CG UEs with the sametime-frequency resources. In such a case, one or more collisions mayoccur. The receiving gNB may identify the UEs involved in a collisionusing other pre-configured resources, e.g., DMRS sequence/index, andresolve the intra-cell collisions in the spatial or code domain.Therefore, resource utilization may be improved despite the bursttraffic and channel availability in NR-U leading to increased usercapacity and reduced latencies.

In an example, dependencies of HARQ process information on the timingmay be removed for NR-U transmission with CG. UCI on PUSCH may carry theHARQ process ID, NDI, RVID as in LTE-AUL. For example, UE may transmitits selected HARQ process ID in a CG-UCI that is multiplexed in thePUSCH. The HARQ process ID may be encoded and decoded separately beforethe data, for example, to enable soft combining of the packet at thegNB. This, however, implies less reliability of the CG-UCI compared to adedicated physical control channel (e.g., PUCCH), for example, becauseof collisions among multiple UE transmissions using the same configuredgrant and/or interference from hidden nodes.

The UE-ID and/or HARQ ID for transmissions using configured grant inNR-U (including initial transmission and retransmissions) may bedetermined based on some flexible mapping mechanism between the HARQ IDand/or UE-ID and the set of configured grant resources/parameters usedfor the transmission of the associated TB. For example, the HARQ processID and/or UE ID may be determined/verified based on the frequencyinterlace and/or the DMRS cyclic shift. This allows for a more flexibleutilization of the configured grant resources and supports multipleresource configuration per cell per UE.

UL transmission collisions may occur, for example, because gNB mayconfigure multiple UEs to share the same configured grant resource. Inan example, configured grant UE may be allocated to occupy parts of thechannel bandwidth. In this case, different UEs may be allocateddifferent interlaces, but LBT may be performed on the whole BWP and/orbandwidth of the channel. If one UE successfully performs LBT earlierand transmits data on the configured BWP, then other UEs may not be ableto access the channel due to LBT failure on the same BWP. Therefore,multiple channel access and/or multiple UL user multiplexing may not beachieved. For example, blank pattern method and/or same UL datatransmission starting point mechanism may be used to reduce ULcollisions. In an example, configured grant UE may be allocated tooccupy the entire channel bandwidth. In this case, the same resource maybe used by other UEs to avoid the resource waste, for example, if thisUE has LBT failure and/or no data to transmit. To alleviate thecollision problem when multiple UEs attempt to access the same CG PUSCHresource, RRC configured starting offset set and/or UE-selected startingoffset from the configured set may be employed.

Configured grant transmissions may involve scheduling multiple UEs onoverlapping resources including possibly with same DMRSsequence/resource. In an example, a UE-ID may be included in the UCIpayload to provide a robust and reliable way for gNB to determine whichUE is transmitting. In an example, orthogonal DMRS sequences may be usedto differentiate UEs. However, configuring multiple orthogonal DMRSsequences may result in higher DMRS overhead and may not always befeasible, for example, when supporting higher rank transmissions on CGPUSCH resources. The presence/absence of UE-ID in the CG-UCI may be RRCconfigured.

It is desirable for gNB to be able to decode UCI and detect DMRS withoutknowing the exact starting point to reduce the blind detectioncomplexity at gNB. Hence, UCI and DMRS may be sent on symbols after alast allowed starting point. Different transmission starting points mayallow later UEs to determine whether the earlier UEs occupy the mediumor not when they are overloaded on the same resource. UEs allocated onorthogonal resources may have the same starting point in order not toblock each other during LBT. For example, when all the frequency domainresources are allocated to a UE, then different UEs may pick differentstarting times (e.g., within the first symbol of the resource) tocontend for transmission. For example, when a subset of the frequencydomain resources are allocated, then the UEs are assigned with a fixedand/or aligned starting position for UL transmission. In NR-U, differentUEs may have different configured BWPs and support both regular andinterlaced waveforms. So it may be possible to have contention-basedtransmissions among UEs that aren't allocated the full set of RB s. InFeLAA, the starting point offset (time domain) is selected randomly froma set of values configured by RRC when the allocation spans the entirebandwidth, but is a fixed value for interlace based partial bandwidthallocation. So the collision between UEs may be avoided for fullbandwidth allocations, and FDM across UEs may be allowed for partialbandwidth allocations.

In an example, CG-UCI may include UE-ID and/or CRC scrambled by specificRNTI to increase the robustness of UCI in case of intra-cell collisionsand/or to identify the UE at the base station. The CG-UCI may bemultiplexed in the CG-PUSCH the same way as HARQ-ACK UCI. The CG-UCI maybe part of HARQ-ACK UCI.

CG-UCI may be mapped on a first symbol after DMRS. DMRS and CG-UCI maybe transmitted on symbol(s) that comprise last allowed starting point.First symbol and last symbol may not be used for DMRS and/or CG-UCI.CG-UCI may be mapped using NR UCI multiplexing rules. CG-UCI may be sentbefore HARQ-ACK/NACK.

It may be feasible to operate single carrier wideband operation when LBTis successful in all LBT subbands. Guardbands may be needed in betweenLBT subbands. In-carrier guardband is defined as guard band between LBTbandwidths in a carrier/BWP, different from guardband at the edge of thecarrier. In-carrier guardbands may be pre-defined and/or configurable bygNB. Availability of in-carrier guardband for PDSCH/CSI-RS may varybased on how much time is elapsed after the start of DL burst.Availability of in-carrier guardband for PDSCH may vary based onfrequency domain channel occupancy structure. Availability of in-carrierguardband for PDSCH may be up to scheduler implementation. Pre-definedin-carrier guardband may always be unavailable for PDCSH.

Single wideband carrier operation may be feasible when LBT is successfulin a subset of the LBT subbands which are contiguous. If PRBs within theguardband of two contiguous LBT subbands are scheduled by gNB, thenfilter adaptation may be needed. Single wideband carrier operation maybe feasible when LBT is successful in a subset of the LBT subbands whichare non-contiguous, at least if PRBs within the guardband of twocontiguous LBT subbands are not scheduled by gNB. Some level ofin-carrier leakage and blocking requirements may be met at the BS andUE.

In an example, multiple active frequency domain configured grantconfigurations per BWP may be supported. For the UL transmission withconfigured grant in NR-U, configuration of frequency domain resourcesmay include one or more frequency interlaces. Frequency domain resourcesmay be configured across multiple subbands of a wideband UL BWPconfigured to the UE for transmission with configured grant in NR-U.Based on the results of the subband LBT procedures, the CG UE maytransmit on one or more subbands, e.g., for which the LBT procedures aresuccessful. Thus, a number of transmission opportunities in frequencydomain may be improved.

For UL transmissions in a serving cell with carrier bandwidth greaterthan LBT bandwidth, for the case when UE performs CCA before ULtransmission, the UE may transmit PUSCH only if CCA is successful at UEin all LBT subbands/bandwidths of the scheduled PUSCH. In an example,the UE may transmit the PUSCH in all or a subset of LBTsubbands/bandwidths of the scheduled PUSCH for which CCA is successfulat the UE. In an example, the subset of LBT subbands/bandwidths maycomprise only contiguous LBT subbands/bandwidths. In an example, thesubset of LBT subbands/bandwidths may comprise non-contiguous LBTsubbands/bandwidths. The scheduled PUSCH may comprise one or moreguardbands in between the LBT subbands/bandwidths.

When GC-PDCCH is configured, explicit indication via GC-PDCCH may beused to inform the UE that one or more carriers and/or LBTsubbands/bandwidths are not available or are available for DL reception,at least for slot(s) that are not at the beginning of DL transmissionburst. UE may adjust monitoring behavior for PDCCH candidate if thePDCCH candidate is mapped fully or partially in LBT bandwidth(s) that isindicated to be unavailable for DL reception by GC-PDCCH. For CORESETconfiguration in a serving cell with carrier bandwidth greater than LBTbandwidth, a CORESET may be configured over multiple LBT bandwidths, ora CORESET may be confined within a LBT bandwidth. For CORESETconfiguration in a serving cell with carrier bandwidth greater than LBTbandwidth, for the case where a CORESET is confined within a LBTbandwidth, the search space set configuration associated with theCORESET may have multiple monitoring locations in the frequency domain(e.g., per LBT subband/bandwidth). For the case in which gNB transmitsPDCCH/PDSCH on a single BWP if CCA is successful at gNB for the wholeBWP, CORESET(s) need not all be confined within an LBT bandwidth. A UEmay receive a PDSCH scheduled within an LBT bandwidth and/or overmultiple LBT bandwidths. A UE capability signaling may indicate maximumsupportable number of CORESETs per BWP.

A bitmap for indicating available subband/carrier information may beprovided per cell in DCI and transmitted on GC-PDCCH. For example, ifmore than one bit is provided for a cell, each bit may represent whetherthe corresponding LBT subband in the corresponding carrier is availablefor DL reception. For example, if only one bit is provided for a cell,the bit may represent whether the corresponding carrier is available forDL reception. Some control information, e.g., COT/SFI duration/endingindication and PDCCH monitoring occasion indication may besubband-specific. Subband-specific control information may be conveyedin group-common DCI. For example, subband-specific control informationmay be provided per subband per cell. For example, subband-specificcontrol information may be provided for certain subband(s) per cell,where the certain subband(s) may be indicated by availablesubband/carrier information. The gNB's transmitted LBT bandwidths and/orcarriers may be explicitly indicated to UE via a bitmap in GC-PDCCHand/or UE-specific PDCCH. The time domain validity of the GC-PDCCHindication of frequency domain channel occupancy may be extended to awhole COT. The UE may obtain the information about LBT outcome in eachsubband based on initial signal e.g. DMRS, for example, when GC-PDCCH isnot configured or not received by the UE, and/or at the beginning of DLtransmission burst. The GC-PDCCH indication time-domain validity mayspan a DL burst(s) within a shared COT.

In an example, configured grant-based and/or dynamically scheduledwideband transmission may span multiple subbands. The subset of LBTsubbands used for CG PUSCH and/or scheduled PUSCH transmission may becontiguous.

A bandwidth occupied by a PUCCH resource on unlicensed band may beconfined within a LBT bandwidth (20 MHz). Frequency domain resourceallocation for a PUCCH transmission may be configured/determined asallocation of interlace(s) by re-interpreting startingPRB in NR PUSCHresource configuration and nrofPRBs in NR PUCCH format configuration,and/or as allocation of a LBT subband by a new field in a PUCCH resourceconfiguration. One or more frequency domain candidate resourcesdistributed in different LBT subbands may be configured for a PUCCHtransmission in NR-U.

In an example, the configured grant retransmission timer value may beconfigured per configured grant configuration, and the configured grantretransmission timer may be maintained per HARQ process. Autonomousretransmission on configured grant resource may be prohibited for a HARQprocess, for example while the configured grant retransmission timer forthe HARQ process is running. New retransmission on configured grantresource may be prohibited for the HARQ process, for example, while theconfigured grant retransmission timer is running because the configuredgrant timer may be running too. The value of configured grantretransmission timer may be shorter than the value of configured granttimer. The configured grant timer may not be restarted at autonomousretransmission on configured grant resource after the configured grantretransmission timer expiry. The UE may not stop the configured granttimer upon NACK feedback reception, and may stop the configured granttimer upon ACK feedback reception. The configured grant timer may not bestarted/restarted when configured grant is not transmitted due to LBTfailure. The configured grant timer may not be started/restarted when ULLBT fails on PUSCH transmission for grant received by PDCCH addressed toCS-RNTI scheduling retransmission for configured grant. The configuredgrant timer may not be started/restarted when the UL LBT fails on PUSCHtransmission for UL grant received by PDCCH addressed to C-RNTI, whichindicates the same HARQ process configured for configured uplink grant.Retransmissions of a TB using configured grant resources, when initialtransmission or a retransmission of the TB was previously done usingdynamically scheduled resources, may not be allowed. On LBT failure attransmission on configured grant, the UE may transmit the pending TBusing same HARQ process in a configured grant resource. CS-RNTI may beused for scheduled retransmission and C-RNTI may be used for newtransmission.

A serving cell may be configured with bandwidth larger than 20 MHz. A UEin unlicensed band should perform clear channel assessment (CCA) rightbefore transmitting to determine whether the channel is idle or not.While a BWP may be configured with a bandwidth larger than 20 MHz, theCCA is performed in 20 MHz units (LBT subband/bandwidth). A UE mayreceive an UL grant or be configured with a CG with a bandwidth largerthan LBT subband. A UE may receive multiple UL grants or be configuredwith multiple CGs for each subband.

In an example, the UE may transmit using the entire allocated bandwidthonly if CCA is successful for all LBT subbands of the allocatedbandwidth. The MAC of the UE may generate a MAC PDU based on the ULresource for the whole allocated bandwidth, and deliver the generatedMAC PDU to lower layer, irrespective of CCA results. In fact, it may notmatter for the MAC layer whether the CCA in PHY layer will be successfulor failed when the delivered MAC PDU is being transmitted. If the CCAfails for at least one of the subbands, the UE may not be able totransmit using the allocated resource on the active BWP. The UE may mostlikely lose the chance of transmission if the channel occupancy rate ofat least one of the subbands is high. If a CCA failure occurs in atleast one of the subbands, the PHY layer of the UE may not transmit theMAC PDU and may receive a UL grant for retransmission of the MAC PDU ormay autonomously retransmit the MAC PDU using configured grant. Then theUE may perform retransmission of the MAC PDU. This approach may bebeneficial for example, when the channel of all allocated subbands islikely to be idle. For example, a base station may acquire a COT on theallocated subbands and share the COT with the UE for UL transmission onthe allocated subbands, in which case the likelihood of CCA success atthe UE is increased. However, the base station may not be able toinitiate and share a COT with the UE and/or predict the CCA result atthe time of UE transmission, which results in the entire resource notbeing used due to CCA failure in a specific subband.

In an example, the UE may perform UL transmission using all or subset ofallocate subbands in which CCA is successful at UE. However, the MACentity of the UE may not be able to generate a MAC PDU based on CCAresults, because the UE should complete the MAC PDU generation, pass theMAC PDU to PHY layer, and then the PHY layer performs CCA. SO the MACPDU generation is done before data transmission and the channel sensingis performed right before transmission.

In an example, the MAC entity may generate a MAC PDU based on thebandwidth of the allocated resource, e.g., comprising multiple subbands.The MAC entity may transmit the generated MAC PDU to the PHY layer. ThePHY layer may generate a TB corresponding to the entire bandwidth of theresource and perform CCA on all allocated subbands. The PHY layer maytransmit the TB on one or more subbands where CCA is successful, and maypuncture/empty the physical resources that overlap with the occupiedsubbands where CCA is failed.

In an example, the MAC entity may generate multiple MAC PDUs of variousversions with different bandwidths suitable for possible resourcescomprising different number of subbands (which may later have successfulCCA). The MAC entity may transmit the generated MAC PDU to the PHYlayer. The PHY layer may generate a TB corresponding to the bandwidth ofthe resource that comprises subband(s) with successful CCA. For example,the UE may perform rate-matching of physical resources for mapping theMACH PDU to subband(s) where CCA is successful. The PHY layer maytransmit the TB the subband(s) where CCA is successful, and may nottransmit anything on subband(s) where CCA is failed. The complexity ofthe MAC layer may be increased by preparing multiple rate-matchedversions.

In an example, the MAC entity may generate a MAC PDU based on thebandwidth of the allocated resource, e.g., comprising multiple subbands.The MAC entity may transmit the generated MAC PDU to the PHY layer. ThePHY layer may generate the TB corresponding to the entire resource. ThePHY layer may only code block(s)/CBG(s) for each subband in which CCA issuccessful. The PHY layer may transmit the TB on one or more subbandswhere CCA is successful, and may puncture/empty the TB on resourceelements that overlap with the occupied subbands where CCA is failed. Ifthe channel for a specific subband is busy, the CBG for that subband maybe retransmitted. The MAC layer may wait until all CBGs are successfullyreceived at the PHY layer.

In an example, the MAC entity may generate multiple MAC PDUs based on ULgrant/resource per subband (e.g., based on a bandwidth of a LBT subband)based on the received multiple UL grants. The MAC entity may transmitthe generated MAC PDUs to the PHY layer. The PHY layer may generate TBscorresponding to each MAC PDU for each UL grant. The PHY layer maytransmit each TB on the subband(s) where CCA is successful, and may nottransmit anything on subband(s) where CCA is failed. UE may performmultiple HARQ processes at a given time for this example.

In an example, the MAC entity may generate a MAC PDU based on ULgrant/resource for a subband (e.g., based on a bandwidth of a LBTsubband). The MAC entity may transmit the generated MAC PDU to the PHYlayer. The PHY layer may generate a TB and may transmit the TB on oneselected subband where CCA is successful, and may not transmit anythingon other subband(s) irrespective of the CCA results. The UE may not usethe whole allocated bandwidth in this example. CCA opportunities may beincreased in this example. The UE may repeatedly transmit the MAC PDU onall subbands in which CCA is successful. However, a channel occupancyrate of all those subbands may be increased in the system.

In unlicensed carriers, a base station may configure multiple UEs withsame time/frequency/spatial resources for configured grant basedtransmissions to avoid resource waste due to burst traffic and/or LBTfailures. In existing technology, a wireless device may transmit uplinkcontrol information (UCI) comprising a UE-ID (e.g., C-RNTI, CS-C-RNTI,etc.), NDI, and/or a HARQ process ID in a configured grant (CG) PUSCHtransmission. The UCI information may be used by the base station toobtain necessary information in performing HARQ operation on the CGPUSCH transmission. For example, the base station may be able toschedule a retransmission corresponding to the CG PUSCH transmission inresponse to successfully determining the HARQ process ID, NDI and the UEID while failing in decoding data carried in the CG PUSCH. Compared todata which may be recovered via HARQ retransmission, a failure of UCItransmission on the CG PUSCH (CG-UCI) may not be recoverable. There is aneed to improve a design of configured grant configuration for enhancedcollision avoidance in unlicensed bands, especially for the CG-UCItransmission that is multiplexed in the CG PUSCH transmission. IncludingCG-UCI in every CG PUSCH transmission results in an increased likelihoodof CG-UCI collision, which yields to base station not being able todecode the entire CG PUSCH transmissions, as the required informationfor decoding the PUSCH is in the CG-UCI which may not be decodable.

Example embodiments propose one or more mechanisms for enhancing areliability of CG-UCI transmission in unlicensed spectrum. In anexample, a wireless device may determine one or more resource elements(REs) to map a CG-UCI in a CG-PUSCH based on one or more criteria. Forexample, the wireless device may determine a first PRB and a last PRBwhere the CG-UCI is mapped based on a starting PRB index of the CG-PUSCHand the UE ID. A first wireless device with a first UE ID may select adifferent frequency location from a second wireless device with a secondID sharing a same time/frequency resource for a first CG-PUSCH by thefirst wireless device and a second CG-PUSCH by the second wirelessdevice. For example, the wireless device may determine the first PRB andthe last PRB where the CG-UCI is mapped based on the starting PRB indexof the CG-PUSCH and an offset configured to the wireless device by abase station. The base station may configure a first offset to a firstwireless device and a second offset to a second wireless device whichmay share same time/frequency resources. In an example, the wirelessdevice may determine the first PRB and the last PRB where the CG-UCI ismapped based on the starting PRB index of the CG-PUSCH and a proximityto a guard band. The wireless device may avoid mapping the CG-UCI nearor on the guard band to minimize interferences. In an example, thewireless device may determine the first PRB and the last PRB and one ormore PRB s in between where the CG-UCI is mapped based on LBT results ofone or more LBT subbands when the CG PUSCH may be scheduled over aplurality of LBT subbands. The wireless device may dynamically adjustlocation of the CG-UCI mapping or spread the CG-UCI over the pluralityof LBT subbands such that the wireless device may transmit the CG-UCIwhen the wireless device transmits the CG-PUSCH. The wireless device maydynamically select the location of the CG-UCI mapping from one or moreLBT subbands with successful LBT. In response to changing the locationof the CG-UCI mapping due to LBT results, the wireless device mayperform CG-UCI overriding (e.g., puncturing) one or more REs of data REsto maintain a reasonable UE complexity.

Example embodiments may reduce potential collisions of a first CG-UCIfrom a first wireless device and a second CG-UCI from a second wirelessdevice sharing a same time/frequency resource. Embodiments may enhance areliability of a CG-UCI transmission in a wideband operation by avoidingmapping the CG-UCI near or on guard band regions and by mapping theCG-UCIs on one or more LBT subbands with LBT success.

A wireless device (UE) may receive one or more messages, e.g., RRCmessages and/or broadcast SIB1 message, from a base station (BS). Theone or more messages may comprise configuration parameters of aconfigured grant resource. The configuration parameters may indicateradio resources of a configured grant. For example, the radio resourcemay be periodic. For example, the radio resources may comprise one ormore LBT subbands in frequency domain. The configuration parameters mayfurther indicate one or more DMRS scrambling ID/sequence number, and/ora frequency offset. The UE may determine one or more REs/PRBs formapping CG-UCI in the CG PUSCH at least based on the frequency offset ofthe configured grant resource.

In an example, a BS may configure DMRS scrambling ID by RRC, where aunique DMRS scrambling ID may be configured to a wireless device. The BSmay be able to distinguish a UE identify from the DMRS scrambling IDused in a CG PUSCH transmission in response to receiving the CG PUSCH.In an example, the BS may configure DMRS scrambling IDs, where a DMRSscrambling ID may be selected by a wireless device or where the DMRSscrambling IDs may not differentiate different UE IDs. The wirelessdevice may carry a UE-ID in a CG-UCI of a CG PUSCH.

In an example, the BS may attempt to decode a CG-UCI prior to decodingof a CG PUSCH with the CG-UCI. A bit size of the CG-UCI may be fixed orthe bit size of the CG-UCI may be determined without decoding the CGPUSCH. The resources for CG-UCI mapping may be deterministic, e.g.,pre-defined and/or configured by BS. In an example, BS may configureflexible transmission occasion candidates within a period, e.g., byconfiguring multiple starting points. The BS may blindly detect theresources on which a CG PUSCH is transmitted, e.g., via DMRS detectionin the CG. The BS may proceed to detection of CG-UCI, e.g., when theDMRS is detected. The BS may obtain the necessary information to decodethe CG PUSCH from the CG-UCI.

In an example, CG-UCI may be mapped from a first non-DMRS symbol after afirst DMRS symbol in CG-PUSCH resource on one or more allocatedsubbands. For example, the CG-UCI may be mapped onto the CG PUSCH in asubband where the channel is sensed to be idle.

In an example, a UE may receive one or more RRC messages indicating oneor more PUCCH resources/PUCCH resource sets on an unlicensed cell. TheUE may be configured with a CG resource configuration wherein the CGresource configuration may overlap partially or fully with the PUCCHresources/PUCCH resource sets. The wireless device may not use one ormore PRBs overlapping with the PUCCH resources/PUCCH resource sets inmapping a CG-UCI. This is to avoid potential collision with a PUCCHtransmission from a second wireless device colliding with a CG-UCItransmission from a first wireless device. The first wireless device mayexclude the one or more PRBs from mapping either UCI or data (e.g., nomapping on the one or more PRBs) at a slot when the overlap occurs.

In an example, a BS may configure one or more PUCCH resources/PUCCHresource sets to a first wireless device on an unlicensed cell. The BSmay not configure the one or more PUCCH resources/PUCCH resource sets toa second wireless device on the unlicensed cell as the unlicensed cellmay be configured as a SCell to the second wireless device. The BS mayconfigure a set of PRBs and/or a set of time durations to the secondwireless device. The second wireless device may not map CG-UCI over REsoverlapping/belonging to the set of PRBs and/or the set of timedurations based on the configuration. The second wireless device may notmap PUSCH over REs overlapping/belonging to the set of PRBs and/or theset of time durations based on the configuration. This is to avoid apotential collision between a PUCCH of the first wireless device and aPUSCH and/or a CG-UCI of the second wireless device.

Embodiments specified in the specification may be applied to other UCItransmission such as HARQ-ACK, CSI, and/or SR transmissions when theother UCI is piggybacked on a PUSCH (regardless CG PUSCH or UL grantbased PUSCH).

In an example, a PUCCH resource may overlap with a PUSCH resource intime domain. The UE may not support simultaneous transmission of PUSCHand PUCCH, whether they are in the same or different serving cell(s).The UE may multiplex the UCI comprising CG-UCI and/or HARQ-ACK and/orCSI report(s) in CG PUSCH. The BS may semi-statically configure by RRCone or more beta-offset values. The one or more beta-offset values mayindicate a coding rate of the CG-UCI and/or HARQ-ACK and/or CSI and/orPUSCH. The UE may use the one or more beta-offset values to determinethe resource elements allocated to CG-UCI and/or HARQ-ACK/CSI part 1/CSIpart 2. For example, for type 2 CG PUSCH, the one or more beta-offsetvalues may be dynamically indicated by the activation DCI. For example,the beta-offset value for HARQ-ACK may be reused for CG-UCI. Forexample, HARQ-ACK/CSI may not be mapped on the resource elementsallocated to CG-UCI. For example, the base station may configure asecond beta-offset for a configured grant resource configuration. Thewireless device may determine a number of REs used for mapping a CG-UCIbased on the second beta-offset. In an example, the CG-UCI may comprisea UE-ID, NDI, and/or a HARQ process ID. Embodiments may not preclude toinclude other information in the CG-UCI. In an example, one or moreinformation of the CG-UCI may be transmitted via a DM-RS of a CG-PUSCHwhere the CG-UCI is piggybacked. For example, there may be a mapping,configured by the base station, between DM-RS scrambling sequence(s) anda UE ID.

FIG. 17 shows an example of UCI mapping in CG PUSCH for NR-U configuredgrant transmission. BS may configure multiple candidate PUSCHtransmission occasions within a CG period. The UE may transmit the CGPUSCH in the second CG transmission occasion in response to thesuccessful LBT which indicates an idle channel before the second CGtransmission occasion. The UE may map the DMRS to the first symbol ofthe CG PUSCH transmission occasion. The UE may map the CG-UCI to a firstnon-DMRS symbol after the first DMRS symbol. The UE may map other UCIs,e.g., comprising HARQ-ACK and/or CSI from the first non-DMRS symbolafter the first DMRS symbol and/or after mapping the CG-UCI. Forexample, the UE may not map the HARQ-ACK/CSI part 1/CSI part 2 on theresource elements allocated for CG-UCI. For example, the CG-UCI andother UCIs (e.g., comprising HARQ-ACK and/or CSI) may be FDMed in one ormore first non-DMRS symbols of the CG-PUSCH. For example, as shown inFIG. 17, CG-UCI and HARQ-ACK are FDMed in the second non-DMRS symbolafter the DMRS symbol, and the CSI is mapped to the third non-DMRSsymbol after the DMRS symbol. The CG PUSCH is mapped to the rest of theresource elements after the UCIs, e.g., CG-UCI and/or HARQ-ACK and/orCSI are mapped.

FIG. 18 shows an example where a base station allocates the same CGPUSCH resource to multiple UEs, e.g., UE1 and UE2. This example shows afirst OFDM symbol (OS #1) of CG PUSCH resource in a 15 kHz subcarrierspacing. In an example, the BS may allocate the entire channel bandwidthto both UEs. In an example, multiple UEs may contend in accessing thecommon CG PUSCH resource. The BS may configure the multiple UEs with aset of starting points within the first symbol. For example, the BS mayconfigure a set of offset values, e.g., a set comprising {16, 25, 34,43, 52, 61} microsecond (us) offset values, to be applied to thestarting of the first OFDM symbol. Each UE may select, e.g. randomly, astarting point from the configured set, to avoid inter-UE blocking. Forexample, UE1 may select 25 us and UE2 may select 43 us. The UEs mayperform LBT at the selected starting points. For example, UE1 may findthe channel idle (successful LBT) and start PUSCH transmission in the CGresource after 25 us from the starting of OS #1, however, UE2 find thechannel busy (failed LBT) after 43 us from the starting of OS #1, e.g.,due to UE1 transmission. As a result, a collision of UE1 and UE2transmission in the common CG may be avoided. However, only onetransmission may be allowed in this case, resulting in a lowchannel/resource utilization.

FIG. 19 shows an example where a base station allocates partialbandwidth of the same CG PUSCH resource to multiple UEs, e.g., UE1 andUE2. For example, the base station may allocate different interlacedresource elements to the multiple UEs. This example shows a first OFDMsymbol (OS #1) of CG PUSCH resource in a 15 kHz subcarrier spacing. Inthis example, the BS may enable UL UE multiplexing, e.g., by configuringthe multiple UEs with fixed and/or aligned starting points. For example,the BS may configure both UEs with stating point of 16 us. Both UEs mayperform LBT at the same time (e.g., 16 us after the starting of OS #1)and find the channel idle (successful LBT). As a result, both UEs maytransmit via orthogonal/FDMed, e.g., interlaced, resource elements inthe common CG resource.

In an example, a plurality of UEs may be allocated with a common CGresource with the same/overlapping resource elements, e.g., samebandwidth and/or same frequency interlace and/or same starting point. Inan example, one or more UEs from the plurality of UEs may transmit viathe same CG resource. In an example, a BS may not be able tosuccessfully receive/decode CG PUSCH transmissions due to collision ofsimultaneous transmissions via overlapped/shared CG resources and/or dueto interference from hidden nodes. In an example, the plurality of UEsmay map the CG-UCI and/or HARQ-ACK and/or CSI in the same way to thesame resource elements of the common CG resource. In an example, the BSmay not be able to successfully decode the CG-UCI of the CG PUSCH due tocollision among multiple UEs and/or interference. As a result, the basestation may lose important information about one or more CGtransmissions (e.g., HARQ process ID, NDI, RV, UE-ID, etc.) from one ormore UEs comprised in one or more CG-UCIs, and thus, fail to decode theCG PUSCH transmissions.

In an example, the base station may be able to identify colliding UEsbased on UE specific and/or orthogonal resources, e.g., FDM interlaceand/or DMRS scrambling ID/sequence. In an example, even though the BSmay be able to identify the colliding UEs, it may not be able tosuccessfully decode the corresponding CG-UCIs. In an example, the BS mayconfigure one or more orthogonal frequency resources, e.g., resourceelements non-overlapping in frequency domain, for CG-UCI and/or HARQ-ACKand/or CSI in a common CG resource, whether with full channel bandwidthallocation and/or partial channel bandwidth allocation. In an example,multiple UEs may map their CG-UCI and/or HARQ-ACK and/or CSI to a commonCG resource differently (e.g., to different resource elements) based onpre-defined rule and/or RRC configuration and/or one or more indicationsfrom the BS. For example, the resource elements for CG-UCI mapping maybe UE-specific resource and/or group common resources. For example, theresource elements may be FDMed and/or TDMed. For example, the FDMedresources may be contiguous in frequency domain or non-contiguous (e.g.,interlaced).

For example, the CG resource may have a bandwidth comprising one or moreLBT subbands. For example, one or more UEs may map the CG-UCI to theentire bandwidth of the CG resource. For example, in a widebandoperation, one or more UEs may map the CG-UCI to different resourceelements in different subbands. For example, the one or more UEs may mapthe CG-UCI to different resource elements spanning the entire CGbandwidth, e.g., over one or more LBT subbands. For example, thedifferent resource elements may not overlap in frequency domain. Forexample, the different resource elements may be confined to one LBTsubband. For example, the different resource elements may not beconfined to one LBT subband. For example, the different resourceelements may be contiguous or non-contiguous in frequency domain. Forexample, the different resource elements may be interlaced across one ormore LBT subband.

FIG. 20 shows an example where BS configures a configured grant resourcewhile allows multiple, e.g. n, UEs multiplexing in the same CG resource.In this example, each UE is allocated with separate (FDMed) resourceelements (REs)/physical resource blocks (PRBs) in the frequency domainfor mapping CG-UCI in a common CG resource. The BS may configure FDMedCG-UCI REs/PRBs for one or more UEs. The CG-UCI REs/PRBs for each/one ormore UE(s) may be contiguous (as shown in the FIG. 20) or non-contiguous(e.g., interlaced). The one or more UEs may map the DMRS and/or otherUCIs (e.g. HARQ-ACK and/or CSI) and/or the PUSCH data to the sameregion/REs/PRBs. For example, UE #1 may map the CG-UCI to the firstFDMed CG-UCI resource (to one or more REs/PRBs associated with CG-UCI UE#1). The UE #1 may start mapping other UCIs, e.g., HARQ-ACK and/or CSI,and/or PUSCH data immediately after the CG-UCI (e.g., after the one ormore REs/PRBs associated with CG-UCI UE #1), e.g., in the same OFDMsymbol. For example, the UE #1 may not map other UCIs and/or PUSCH datato one or more REs/PRBs allocated for other UEs CG-UCI. For example, UE#1 may empty the REs/PRBs associated with/allocated to CG-UCI UE #2 toCG-UCI UE #n. For example, the UE #1 may start mapping other UCIs and/orPUSCH data after a last FDMed RE/PRB of the CG-UCI REs/PRBs, e.g.,allocated to a last UE (UE #n). For example, each UE may map the CG-UCIto the allocated REs/PRBs and may not map other UCIs and/or PUSCH datato the REs/PRBs allocated to any CG-UCI (e.g., of other UEs). Forexample, the BS may indicate a reference RE/PRB for the one or more UEsto start mapping other UCIs and/or PUSCH data after the CG-UCI. Forexample, the reference RE/PRB may be a first RE/PRB in the CG resourceafter a last RE/PRB allocated to a CG-UCI transmission, in a same symbolor a next symbol. The CG-UCI REs/PRBs for each/one or more UE(s) may bemapped across one or more LBT subbands, e.g., based on a CG PUSCHbandwidth. For example, for wideband CG (e.g., when CG bandwidthcomprises two or more LBT subbands) the CG-UCI mapping may be the same(e.g., as shown in FIG. 20). In an example, a BS may configure an offset(e.g., 0 for UE #1, K for UE #2, 2K for UE #3, and so on in FIG. 20) toa wireless device. The wireless device may determine a starting PRB fora CG-UCI based on a starting PRB of a CG PUSCH and the offset (e.g., afirst PRB of the CG PUSCH for UE #1, a K-th PRB of the CG PUSCH for UE#2, and so on). The base station may additionally configure a number ofPRBs and/or a number of OFDM symbols used for the CG-UCI mapping. Thismay define a number of REs used for the CG-UCI which performs a similarfunction to a beta-offset parameter. Based on configurations, a firstCG-UCI of a first wireless device may overlap or may not overlap with asecond CG-UCI of a second wireless device.

FIG. 21 shows an example where non-contiguous (e.g., interlaced) FDMedresources are allocated for CG-UCI of one or more UEs configured withthe same CG resource. In this example, a size of the entire regionallocated to CG-UCI is fixed and known to the one or more UEs. In thisexample, the one or more UEs map other UCIs and/or PUSCH data to thesame region/REs/PRBs starting after the whole CG-UCI region/bandwidth.This example avoids empty regions within the CG-UCI symbol by spreadingeach CG-UCI across the whole bandwidth allocated to CG-UCIs.

The BS may indicate one or more frequency offsets to one or more UEs toindicate a first allocated RE/PRB for CG-UCI of the one or more UEswithin a common CG resource. The one or more frequency offsets may bewith respect to a starting RE/PRB/subcarrier of the CG resource. The oneor more frequency offsets may be with respect to a reference PRB of thesubband/bandwidth part (e.g. first PRB of a subband, or PRB0 of abandwidth part). The one or more frequency offsets may be with respectto a reference PRB of an uplink cell (e.g., point A indicated in a SIB,by RRC signaling for the UL cell). The one or more frequency offsets maybe with respect to a reference PRB excluding/after the PRBs associatedwith one or more guard bands of the carrier/BWP/subband. For example, awireless device may need K PRBs in each LBT subband (e.g., K/2 PRBs ineach side of the LBT subband). K PRBs may be determined based on a UEcapability. K PRBs may be determined based on a RSRP of an unlicensedcell. K PRBs may be fixed. K PRBs may be determined based on a UEallowed power (e.g., 5 PRBs for 23 dBm allowed power, 10 PRBs for 30 dBmallowed power). For example, K PRBs may be determined based on anumerology used in the unlicensed cell. The wireless device may map dataover the guard-band of a LBT subband. The wireless device may not map aUCI (e.g., CG-UCI) over the guard-band of the LBT subband. The one ormore frequency offsets may be configured such that the CG-UCIs are notmapped to one or more REs/PRBs of one or more guardbands, e.g.,in-carrier and/or edge of carrier guardbands. For example, UE may notmap CG-UCI to one or more REs/PRBs that overlap with guardbands, e.g.,in-carrier guardbands and/or carrier edge guardbands. The wirelessdevice may transmit a UE capability of K PRBs (e.g., a guard band size)to the base station. The K PRBs may be based on a reference numerology(e.g., 15 kHz) and may be assumed to have a same size (e.g., 2K PRBswith 30 kHz) for different numerologies. The wireless device maytransmit a guard band size for a numerology.

In an example, a base station may configure an offset to avoid mappingof a CG-UCI over a guard band in consideration of a RSRP. The basestation may configure a set of {an offset, a RSRP threshold}. Thewireless device may select the offset based on a RSRP of a cell. Forexample, if the RSRP exceeds the RSRP threshold, the wireless device mayselect the offset. The wireless device may select a smallest offset ifthere are multiple pairs satisfied. In an example, an offset may be aLBT subband index. In an example, a wireless device may be configuredwith an offset and a RSRP threshold. The wireless device may determineresources for a CG-UCI mapping based on the offset in response to a RSRPexceeding the RSRP threshold. The wireless device may not apply theoffset in otherwise.

In an example, the CG-UCI partitioning may be per UE and/or group ofUEs. For example, each CG-UCI resource may be explicitly and/orimplicitly mapped to one or more UE-IDs and/or one or more DMRSscrambling IDs and/or one or more HARQ processing IDs and/or one or moreRSRP intervals/thresholds.

For example, one or more frequency/PRB offsets may be pre-defined. Forexample, the BS may configure the one or more frequency offsets via RRCsignaling. For example, the BS may indicate the one or more frequencyoffsets via DCI (e.g., activation DCI for CG type 2). For example, theone or more frequency offsets may be implicitly indicated to a UE. Forexample, the UE may determine the one or more frequency offsets based onone or more pre-configured and/or pre-defined values, e.g. a DMRSscrambling ID/sequence number and/or UE-ID and/or HARQ ID. For example,a mapping function and/or table may be defined between DMRS scramblingID and/or UE-ID and/or HARQ ID and one or more frequency/PRB offsetsand/or interlace patterns. For example, a number of PRBs allocated toone or more UE for CG-UCI may be indicated, e.g. by one or moreparameters. The one or more parameters may be one or more beta-offsetvalues. For example, the BS may indicate, via RRC/DCI signaling, the oneor more beta-offset values. For example, the one or more beta-offsetvalues may be a function one or more DMRS scrambling IDs. For example,the BS may configure similar beta-offset value for all FDMed CG-UCIregions/REs/PRBs. For example, the CG-UCI beta-offset value may be thesame as HARQ-ACK beta-offset value.

In an example, a base station may configure one or more CG-UCIregions/REs/PRBs within a CG resource for partitioning, e.g. infrequency domain, the CG-UCI transmissions of a plurality of UEs basedon their RSRP. For example, the base station may indicate/configure oneor more RSRP threshold and indicate a mapping of CG-UCI region, e.g.,PRB offset, to one or more RSRP intervals. A UE measure a RSRP andcompare it to the one or more RSRP threshold. The one or more RSRPthresholds may be pre-defined. The UE may determine a firstfrequency/PRB offset and/or a first interlace pattern if, for example,the RSRP is above a first threshold and/or below a second threshold. TheUE may map the CG-UCI in the CG PUSCH based on the first frequencyoffset and/or first interlace pattern. For example, the base station mayallocate a first CG-UCI region, e.g. one or more REs/PRBs, to one ormore center UEs with higher RSRP values, and a second CG-UCI region toone or more edge UEs (e.g., far UEs near the edge of the cell) withlower RSRP values. As a result, a reliability of edge UE CG-UCItransmission is enhanced, by ensuring center UEs CG-UCI transmissionusing the same CG resource, who have higher received power at the BS,may not collide/interfere. For example, a frequency/PRB offset from theguardband(s) associated with an edge UE may be larger than a center UE,e.g. to provide the edge UE with a better channel.

A UE may receive one or more messages comprising configurationparameters indicating radio resources of a configured grant. The radioresources may be periodic. The radio resources may comprise a first CGresource, e.g., a time/frequency resource, that spans over two or moreLBT subbands. For example, the first CG resource may be a widebandresource, configured for a wideband operation scenario. Theconfiguration parameters may further indicate one or more DMRSscrambling ID/sequence, and/or one or more frequency/PRB offsets formapping CG-UCI in the CG PUSCH. For example, each of the one or morefrequency/PRB offsets may indicate a CG-UCI region comprising one ormore REs/PRBs (e.g., in a first non-DMRS symbol of the PUSCH).

The first CG resource may comprise one or more CG-UCI regions, e.g.,each CG-UCI may be in one of the two or more LBT subbands. Each of theone or more frequency/PRB offsets may indicate a CG-UCI region in eachof the two or more subbands. For example, the one or more frequencyoffsets may be different or may be the same. For example, one or morebeta-offset values associated with number of PRBs allocated to a CG-UCIin each LBT subband may be different or may be the same. For example,the CG-UCI region in each subband may exclude the in-carrier guardbandsin between the subbands and/or carrier edge guardbands. For example, theUE may not map the CG-UCI to one or more PRBs overlapping withguardbands. The one or more CG-UCI regions may be confined to a subbandbandwidth. In an example, the BS may configure one CG-UCI region for thefirst CG resource. The one CG-UCI region may be confined to a bandwidthof one subband. The one CG-UCI region may span over entire bandwidth ofthe first CG resource. The one CG-UCI region may span over two or moresubbands of the first CG resource.

FIG. 22 shows an example where the UE maps a CG-UCI to a CG-UCI regioncomprising one or more REs/PRBs in a first subband of two or moresubbands within the CG PUSCH bandwidth. The UE may multiplex the CG-UCIin the PUSCH within the first subband. For example, the UE may performrate-matching for multiplexing the CG-UCI. For example, the UE maypuncture/empty one or more first REs of the CG PUSCH resource on thefirst subband allocated to CG-UCI, and adjust a data rate/encoding rateon one or more second REs of the CG PUSCH resource, and encode theCG-UCI on the one or more first REs. For example, the UE may performpuncturing for multiplexing the CG-UCI. For example, the UE maypuncture/empty one or more REs of the CG PUSCH resource on the firstsubband allocated to CG-UCI, and encode the CG-UCI on the one or moreREs.

The first subband may be a subband with a smallest index than othersubbands in the CG PUSCH bandwidth/BWP. The first subband may beindicated by the BS. For example, the BS may send a DCI indicating a COTsharing with the UE on one or more of the subbands comprising the firstsubband. For example, the BS may indicate the first subband viasemi-static configuration. The UE may select the first subband e.g.,randomly. The UE may select the first subband based on at least one ofthe following: a congestion level of the first subband being less thanother subbands; and/or a RSRP in the first subband being greater thanother subbands; and/or a LBT failure counter of the first subband beingless than other subbands; and/or a LBT failure timer of the firstsubband being shorter or longer than other subbands; and/or a channeloccupancy ratio of the first subband being smaller than other subbands;and/or a guardband size of the first subband being smaller than othersubbands.

The bandwidth of the CG resource may comprise two or more subbands. TheUE may map the CG-UCI on one or more REs/PRBs allocated to CG-UCI on afirst subband. The UE may map the PUSCH data on REs (after the CG-UCIREs) of the two or more subbands. For example, the UE may performrate-matching of the PUSCH to map/multiplex the CG-UCI in the PUSCH. TheUE may multiplex the CG-UCI in the CG PUSCH. The UE may perform one ormore LBTs on the two or more subbands of the CG PUSCH bandwidth. The UEmay transmit the CG-UCI and/or PUSCH in one or more subbands where LBTis successful (channel is idle). For example, the UE may transmit theCG-UCI if the LBT in the first subband is successful. For example, theUE may not transmit the CG-UCI if the LBT in the first subband isfailed. For example, the UE may drop the CG-UCI.

FIG. 23 shows an example where the UE maps/multiplexes the CG-UCI on oneor more REs in the first subband (subband1) and performs LBT. In thisexample, the LBT result is failed in subband1 and subband2, and issuccessful in subband3 and subband4. The UE may perform no transmission,e.g., no CG-UCI and/or PUSCH transmission, in the subbands with failedLBT (e.g., subband1 and subband2). For example, the UE maypuncture/empty/vacate the PUSCH data on the subbands with failed LBTsubbands. The UE may place the CG-UCI in one or more REs of one or moresubbands with successful LBT results (e.g. subband3 and/or subband4),e.g., by puncturing and/or rate-matching the PUSCH data around the oneor more REs. For example, only one subband that is not the first subbandmay have successful LBT, and the UE may map the CG-UCI on that subband.For example, LBT may fail on all subbands and UE may drop the PUSCH andCG-UCI transmission. For example, two or more subbands not comprisingthe first subband may have successful LBTs (e.g., subband3 andsubband4). The UE may have not multiplexed the CG-UCI on REs in the twoor more subbands with successful LBT. In response to the LBT failure inthe first subband, the UE may multiplex the CG-UCI in one or moreREs/PRBs in one or more subbands of the two or more subbands. Forexample, the UE may select a second subband (subband3 in FIG. 23) fromthe two or more subbands, and multiplex the CG-UCI in REs in the secondsubband, e.g. by puncturing the REs in the second subband. The UE maynot change a mapping of data to resources regardless of LBT results andregardless of a new LBT subband used for the CG-UCI mapping. Thewireless device may override the CG-UCI over data REs (e.g., puncturing)on the new LBT subband. The UE may transmit the CG-UCI on the secondsubband.

In case the LBT in the first subband fails and the LBT in the two ormore subbands excluding the first subband succeed, the UE may select asecond subband from the two or more subbands. The UE may select thesecond subband based on at least one of the following: a congestionlevel of the second subband being less than other subbands; and/or aRSRP in the second subband being greater than other subbands; and/or aLBT failure counter of the second subband being less than othersubbands; and/or a LBT failure timer of the second subband being shorteror longer than other subbands; and/or a channel occupancy ratio of thesecond subband being smaller than other subbands; and/or a guardbandsize of the second subband being smaller than other subbands. The secondsubband may be a subband with a smallest index among the two or moresubbands. The second subband may be indicated by the BS. For example,the BS may send a DCI indicating a COT sharing with the UE on one ormore of the subbands comprising the second subband. For example, the BSmay indicate the second subband via semi-static configuration. The UEmay select the second subband randomly.

By mapping/multiplexing the CG-UCI to REs in one subband, the UE mayhave more available bits for encoding PUSCH data and/or other UCIscomprising HARQ-ACK and/or CSI, compared to the case that UEmaps/multiplexes the CG-UCI in REs across multiple subbands. However,due to puncturing, a reliability of the CG PUSCH transmission may bealleviated.

In an example, the UE may map/multiplex the CG-UCI in a CG PUSCH thatspans over two or more subbands. The UE may multiplex/map the CG-UCIin/onto at least one of the two or more subbands. The UE maymultiplex/map the CG-UCI in/onto the two or more subbands. The UE maymap same encoded bits of CG-UCI, e.g. repeatedly, on each of the two ormore subbands. For example, the UE may map the CG-UCI on one or moreREs/PRBs in each of the two or more subbands. For example, a number ofREs/PRBs for CG-UCI mapping in each of the tow or more subbands may bethe same or different. For example, a frequency/PRB offset to the one ormore REs/PRB s in each of the two or more subbands may be the same ordifferent. For example, the BS may indicate the size, e.g. a number ofREs/PRBs for CG-UCI mapping, and/or the frequency/PRB offset to the oneor more REs/PRBs in each of the two or more subbands. For example, theREs/PRBs in the two or more subbands may be contiguous and/ornon-contiguous. For example, the UE may map the CG-UCI for one or moretimes on the REs/PRBs across the two or more subbands, e.g. byinterlacing. This may increase a robustness of the CG-UCI transmissionby utilizing channel diversity across subbands.

In an example, a bandwidth of a first CG resource may comprise a firstsubband and a second subband. The UE may map/multiplex the CG-UCI of thePUSCH in the first CG resource. The UE may multiplex the CG-UCI as afirst CG-UCI in one or more REs/PRBs of the first subband with a firstfrequency/PRB offset and/or as a second CG-UCI in one or more REs/PRB sof the second subband with a second frequency/PRB offset. The UE mayperform one or more LBTs in the channel(s) of the first subband and thesecond subband. The UE may transmit the CG PUSCH and/or the CG-UCI on atleast one of the first subband and the second subband where the one ormore LBTs are successful. The UE may perform rate-matching of the CGPUSCH in the first subband and the second subband for multiplexing theCG-UCI. For example, the UE may puncture one or more first REs of one ormore PRBs in the first subband and the second subband, and adjust adata/encoding rate on one or more second REs of the one or more PRBs inthe first subband and the second subband, and encode the CG-UCI on theone or more first REs. The UE may do the same for other UCIs, e.g.HARQ-ACK and/or CSI. For example, the UE may map/multiplex the otherUCIs in the PUSCH in the same way as CG-UCI, e.g., across the two ormore subbands, e.g., repeatedly and/or by interleaving.

FIG. 24 shows as an example where the UE maps/multiplexes the CG-UCIrepeatedly, e.g. on same number of REs/PRBs and with same PRB offset,across four subbands of the CG PUSCH bandwidth (subband1 and subband2and subband3 and subband4). The UE may map an encoded UCI bits startingfrom a first subband in an interlaced manner (e.g., a first RE of afirst PRB of a first subband, a first RE of a first PRB of a secondsubband, a first RE of a first PRB of a third subband, . . . , a secondRE of the first PRB of the first subband, a second RE of the first PRBof the second subband, . . . , a first RE of a second PRB of the firstsubband, a first RE of a second PRB of the second subband, . . . , andso on). This interleaving may randomize interferences on a subband.

FIG. 25 shows an example where a number of PRBs of the CG-UCI (e.g. abeta-offset for multiplexing the CG-UCI) and/or a PRB offset formultiplexing the CG-UCI in each subband are different.

FIG. 26 shows an example where the UE prepares four CG-UCI parts/PRB(s),e.g. CG-UCI 1, CG-UCI 2, CG-UCI 3, and CG-UCI 4. For example, the CG-UCImay comprise the four CG-UCI parts/PRB(s). For example, the four CG-UCIparts/PRB(s) may be different portions of the CG-UCI. For example, eachof the CG-UCI parts/PRB(s) may comprise one or more PRBs. The UE may mapeach CG-UCI part/PRB(s) differently in each subband. For example, the UEmay use different interlace/interleaving pattern(s) for the CG-UCI ineach subband. For example, a PRB offset for mapping a CG-UCI part/PRB(s)in each subband may be different. For example, assuming each CG-UCI partin FIG. 26 is one PRB, the CG-UCI 1 is mapped with: a PRB offset of zeroin subband 1, a PRB offset of one in subband 2, a PRB offset of two insubband 3, and a PRB offset of three in subband 4. Different PRB offsetsmay be used for mapping different CG-UCI and/or other UCIs in each ofthe two or more subbands.

A UE may map/multiplex the CG-UCI and/or other UCIs (e.g., HARQ-ACK, CSIpart 1, CSI part 2, SR, etc.) in one or more PRBs across two or moresubbands within a CG PUSCH. The UE may multiplex the CG-UCI byrate-matching and/or puncturing of the PUSCH in each subband. The UE mayperform one or more LBTs in the two or more subbands for transmittingthe CG PUSCH and/or the CG-UCI and/or other UCIs on the PUSCH.

For example, the result of the one or more LBTs may indicate channel(s)of the two or more subbands are idle/available. For example, the one ormore LBTs may be successful in the two or more subbands. In that case,the UE may transmit the CG-UCI and/or the CG PUSCH and/or other UCIs viaone or more PRBs over the two or more subbands. For example, the basestation may receive two or more copies of the CG-UCI in the two or moresubbands. For example, the CG-UCI in each subband may be interleaved.For example, the CG-UCI may be interlaced across the two or moresubbands. The BS may be able to decode the CG-UCI by combining the twoor more copies of the CG-UCI from the two or more subbands, with higherprobability of successful decoding. For example, if the channel in ofthe subbands is bad, the BS may not be able to successfully decode theCG-UCI in that subband. For example, using the channel diversity acrossthe two or more subbands may help the BS successfully decode the CG-UCIby combining the two or more received versions of the CG-UCI from thetwo or more subbands.

In an example, the result of the one or more LBTs may indicatechannel(s) of the two or more subbands are busy/occupied/unavailable.For example, the one or more LBTs may be failed in the two or moresubbands. In that case, the UE may not transmit the CG-UCI and/or the CGPUSCH and/or other UCIs via one or more PRBs over the two or moresubbands.

In an example, the result of the one or more LBTs may indicatechannel(s) of at least one of the two or more subbands areidle/available. For example, the one or more LBTs may be successful inthe at least one of the two or more subbands. In that case, the UE maytransmit the CG-UCI and/or the CG PUSCH and/or other UCIs via one ormore PRBs over the at least one of the two or more subbands. Forexample, the UE may transmit the CG-UCI and/or the CG PUSCH and/or otherUCIs via one or more PRBs over a first subband of the at least one ofthe two or more subbands. For example, the UE may puncture/vacate theREs/PRBs of one or more subbands where the LBT is failed.

In an example, multiplexing CG-UCI over two or more subbands of the CGPUSCH may increase a likelihood of CG-UCI transmission despite LBTfailure in one or more of the tow or more subbands. In an example,multiplexing the CG-UCI over the two or more subbands of the CG PUSCH byrate-matching of the PUSCH may be better than multiplexing the CG-UCI inone subband of the CG PUSCH, because of a likelihood of LBT failure. AUE may multiplex the CG-UCI in one subband of the CG PUSCH, and if LBTfails on the one subband, the UE may multiplex the CG-UCI in a secondsubband of the CG PUCH by puncturing the PUSCH in the second subband.However, that may result in an alleviated transmission of the PUSCH assome of the PUSCH data is removed on the fly. It may be better if the UEmultiplexes one or more versions of the CG-UCI (e.g., with one or moreencoding rates and/or one or more offsets and/or one or more interlacepatterns, etc.) in PRBs of the two or more subbands, as there would beno need for removing/puncturing data on the fly, and a rate of dataencoding may be matched/adjusted to allow for multiplexing the CG-UCIwithout any need to lose data bits. For example, a BS may receive atleast one copy/version of the CG-UCI if LBT is successful in at leastone of the subbands of the CG. Thus, a likelihood of CG-UCItransmission/reception is increased. The BS may receive two or morecopies/versions of the CG-UCI via two or more subbands of the CG. Thus,a likelihood of successful decoding of the CG-UCI is enhanced by, e.g.,combining the received bits from the two or more subbands.

A wireless device may receive one or more messages comprisingconfiguration parameters of radio resources of a configured grant. Theradio resources may comprise a first radio resource spanning over afirst subband and a second subband. The wireless device may multiplexthe CG-UCI of PUSCH transmission in the first resource. The CG-UCI maybe multiplexed as a first UCI in one or more first resource blocks ofthe first subband with a first frequency offset; and as a second UCI inone or more second resource blocks of the second subband with a secondfrequency offset. The wireless device may transmit, via the firstresource, at least one of the first UCI and the second UCI based on oneor more LBT procedures performed on the first subband and the secondsubband. The first UCI and the second UCI may be the same. The first UCImay comprise a first part of the CG-UCI and the second UCI may comprisea second part of the CG-UCI. The first frequency offset and the secondfrequency offset may be with respect to a reference resource block of aBWP comprising/associated with the first subband and the second subband.The first frequency offset and the second frequency offset may be withrespect to a reference resource block of the first resource. The firstfrequency offset and the second frequency offset may be the same. Thefirst frequency offset and the second frequency offset may be greaterthan a bandwidth of a guardband of the first subband and the secondsubband. The first subband and the second subband may be contiguous ornon-contiguous. The wireless device may transmit the first UCImultiplexed in the PUSCH transmission in the first subband in responseto the one or more LBT procedures indicating the first subband is idle.The wireless device may transmit the second UCI multiplexed in the PUSCHtransmission in the second subband in response to the one or more LBTprocedures indicating the second subband is idle. The wireless devicemay transmit the first UCI multiplexed in the PUSCH transmission in thefirst subband in response to the one or more LBT procedures indicatingthe first subband is idle. The wireless device may puncture a part ofthe first resource overlapped with the first/second subband in responseto the one or more LBT procedures indicating that the first/secondsubband is occupied. The wireless device may not perform the PUSCHand/or CG-UCI transmission in the first/second subband in response tothe one or more LBT procedures indicating that the first/second subbandis occupied. The wireless device may transmit the first UCI and thesecond UCI multiplexed in the PUSCH transmission in the first subbandand the second subband in response to the one or more LBT proceduresindicating that the first subband and the second subband are idle. Thefirst resource may comprise one or more slots and/or one or more symbolsand one or more resource blocks and/or one or more subcarriers. Thefirst resource block and the second resource block may correspond to oneor more first symbols of the first resource. For example, the firstresource block and the second resource block may correspond to a firstnon-DMRS symbol of the first resource. The one or more first symbols maycomprise a first symbol after a demodulation reference signal symbol.

A wireless device may receive one or more messages comprisingconfiguration parameters of radio resources of a configured grant. Theradio resources may comprise a first resource spanning over a firstsubband and a second subband. The wireless device may multiplex, using afirst multiplexing procedure, UCI of a PUSCH transmission in a firstresource block of the first resource in the first subband. The wirelessdevice may determine switching to a second multiplexing procedure formultiplexing the UCI of the PUSCH in a second resource block of thefirst resource in the second subband, for example, based on one or moreLBT procedures indicating the first subband is occupied and the secondsubband is idle. The wireless device may transmit the PUSCH and/or themultiplexed UCI via the second resource block. The first multiplexingprocedure may comprise rate-matching of the PUSCH. For the firstmultiplexing procedure the wireless device may puncture one or morefirst radio elements of the first resource block and adjustdata/encoding rate on one or more second radio elements of the firstresource block and encode the UCI on the one or more first radioelements. The first multiplexing procedure may comprise puncturing ofthe PUSCH. For the first multiplexing procedure the wireless device maypuncture one or more radio elements of the first resource block andencode the UCI on the one or more radio elements. For the secondmultiplexing procedure the wireless device may puncture one or morefirst radio elements of the second resource block and adjustdata/encoding rate on one or more second radio elements of the secondradio resource block and encode the UCI on the one or more first radioelements. The second multiplexing procedure may comprise puncturing ofthe PUSCH. For the second multiplexing procedure the wireless device maypuncture one or more radio elements of the second resource block andencode the UCI on the one or more radio elements. The UCI may be aCG-UCI and/or HARQ-ACK and/or CSI.

A wireless device may receive one or more messages comprisingconfiguration parameters indicating radio resources of a configuredgrant and a frequency offset. The wireless device may determine a radioelement for a CG-UCI based on a reference resource block of one of theradio resources of the configured grant and the frequency offset. Thewireless device may multiplex the CG-UCI in PUSCH of the configuredgrant, starting from the radio element. The wireless device may transmitvia the one of the radio resources the CG-UCI multiplexed in the PUSCHand/or the PUSCH. The wireless device may determine the frequency offsetbased on a DMRS sequence number/scrambling ID of the radio resources ofthe configured grant. The one or more messages may further indicate theDMRS sequence number/scrambling ID. The DMRS sequence number/scramblingID may be mapped to one or more values comprising the frequency offset.For example, a first DMRS sequence number/scrambling ID may indicate afirst frequency/PRB offset. The wireless device may determine thefrequency offset based on a RSRP. For example, the wireless device maydetermine a first frequency offset in response to the RSRP being lowerthan a value, and a second frequency offset in response to the RSRPbeing higher than the value. The radio element for CG-UCI may notoverlap with one or more resource blocks of a guardband. The wirelessdevice may determine the radio element for the CG-UCI based on applyingthe frequency offset with respect to a reference resource block of theone of the radio resources of the configured grant. The referenceresource block may be a first resource block of the one of the radioresources of the configured grant after one or more resource blocks of aguardband. The radio resources of the configured grant may span over oneor more BLT subbands.

A base station may determine configuration parameters of a configuredgrant. The configuration parameters may indicate radio resources of theconfigured grant and one or more frequency offsets indicating one ormore radio elements of the radio resources for receiving one or moreCG-UCIs multiplexed in one or more PUSCHs. The base station maydetermine each of the one or more frequency offsets based on one or moreDMRS sequence numbers/scrambling IDs. For example, for a first DMRSsequence number/scrambling ID, the base station may determine a firstfrequency offset. The base station may determine the one or morefrequency offset based on one or more ranges of RSRP values. Forexample, for a first range of RSRP, the base station may determine afirst frequency offset. The base station may determine the one or morefrequency offsets based on one or more UE-IDs. The base station maydetermine the one or more frequency offsets based on bandwidth of one ormore guardbands. The base station may transmit to one or more wirelessdevices one or more messages comprising the configuration parameters.The base station may receive from at least one of the one or morewireless devices and via the one or more radio elements, the one or moreCG-UCIs each multiplexed in a PUSCH transmission.

According to various embodiments, a device such as, for example, awireless device, off-network wireless device, a base station, and/or thelike, may comprise one or more processors and memory. The memory maystore instructions that, when executed by the one or more processors,cause the device to perform a series of actions. Embodiments of exampleactions are illustrated in the accompanying figures and specification.Features from various embodiments may be combined to create yet furtherembodiments.

FIG. 27 is an flow diagram as per an aspect of an example embodiment ofthe present disclosure. At 2710, a wireless device may receiveconfiguration parameters of periodic radio resources of a configureduplink grant. The periodic radio resources may comprise: one or morefirst resource elements of a first sub-band; and one or more secondresource elements of a second sub-band. At 2720, a wireless devicemultiplexing: a first configured grant uplink control information(CG-UCI) via the one or more first resource elements; and a secondCG-UCI via the one or more second resource elements. The second CG-UCImay be based on a repetition of the first CG-UCI. At 2730, at least oneof the first CG-UCI and the second CG-UCI may be transmitted via theperiodic radio resources and based on one or more listen-before-talk(LBT) procedures performed on the first sub-band and the secondsub-band.

According to various embodiment, multiplexing a CG-UCI may comprisemultiplexing control bits for the CG-UCI onto data bits for a physicaluplink shared channel (PUSCH), and a length of the control bits isdetermined based on a number of resource elements that can be used fortransmission of the CG-UCI. According to various embodiments, thewireless device may determine, based on a first frequency offset and anumber of the one or more first resource elements, a first length offirst control bits for the first CG-UCI. According to variousembodiment, the wireless device may determine, based on a secondfrequency offset and a number of the one or more second resourceelements, a second length of second control bits for the second CG-UCI.

According to various embodiments, the wireless device may transmit thePUSCH via the periodic radio resources of the configured uplink grantand based on the one or more LBT procedures performed on the firstsub-band and the second sub-band. According to various embodiments, thefirst CG-UCI and the second CG-UCI may comprise one or more hybridautomatic repeat request (HARD) process identifiers of the PUSCH.According to various embodiments, the first CG-UCI and the second CG-UCImay comprise one or more indicators indicating whether the PUSCHcorresponds to new data. According to various embodiments, the firstCG-UCI and the second CG-UCI may comprise one or more redundancyversions of the PUSCH. According to various embodiments, the firstCG-UCI and the second CG-UCI may comprise channel occupancy timeinformation.

According to various embodiments, the transmitting may comprisetransmitting, in response to the one or more LBT procedures indicatingthe first sub-band and the second sub-band are idle: the first CG-UCIvia the first sub-band; and the second CG-UCI via the second sub-band.According to various embodiments, in response to the one or more LBTprocedures indicating the first sub-band is occupied and the secondsub-band is idle: the first CG-UCI may not be transmitted via the firstsub-band. According to various embodiments, in response to the one ormore LBT procedures indicating the first sub-band is occupied and thesecond sub-band is idle, the second CG-UCI may be transmitted via thesecond sub-band.

According to various embodiments, the first sub-band and the secondsub-band may comprise resource blocks of a bandwidth part. According tovarious embodiments, the first sub-band and the second sub-band may beadjacent. According to various embodiments, the one or more firstresource elements and the one or more second resource elements mayexclude one or more third resource elements of at least one guard-bandbetween the first sub-band and the second sub-band.

What is claimed is:
 1. A method comprising: receiving, by a wirelessdevice, configuration parameters of periodic radio resources of aconfigured uplink grant, wherein the periodic radio resources comprise:one or more first resource elements of a first sub-band; and one or moresecond resource elements of a second sub-band; multiplexing: a firstconfigured grant uplink control information (CG-UCI) based on the one ormore first resource elements; and a second CG-UCI based on the one ormore second resource elements, wherein the second CG-UCI is based on arepetition of the first CG-UCI; and transmitting, via the periodic radioresources and based on one or more listen-before-talk (LBT) proceduresperformed on the first sub-band and the second sub-band, at least one ofthe first CG-UCI and the second CG-UCI.
 2. The method of claim 1,wherein multiplexing a CG-UCI comprises multiplexing control bits forthe CG-UCI onto data bits for a physical uplink shared channel (PUSCH),and a length of the control bits is determined based on a number ofresource elements that can be used for transmission of the CG-UCI. 3.The method of claim 2, further comprising determining: based on a firstfrequency offset and a number of the one or more first resourceelements, a first length of first control bits for the first CG-UCI; andbased on a second frequency offset and a number of the one or moresecond resource elements, a second length of second control bits for thesecond CG-UCI.
 4. The method of claim 2, further comprising transmittingthe PUSCH via the periodic radio resources of the configured uplinkgrant and based on the one or more LBT procedures performed on the firstsub-band and the second sub-band.
 5. The method of claim 4, wherein thefirst CG-UCI and the second CG-UCI comprise at least one of: one or morehybrid automatic repeat request (HARD) process identifiers of the PUSCH;one or more indicators indicating whether the PUSCH corresponds to newdata; one or more redundancy versions of the PUSCH; and channeloccupancy time information.
 6. The method of claim 1, wherein thetransmitting comprises transmitting, in response to the one or more LBTprocedures indicating the first sub-band and the second sub-band areidle: the first CG-UCI via the first sub-band; and the second CG-UCI viathe second sub-band.
 7. The method of claim 1, further comprising, inresponse to the one or more LBT procedures indicating the first sub-bandis occupied and the second sub-band is idle: not transmitting the firstCG-UCI via the first sub-band; and transmitting the second CG-UCI viathe second sub-band.
 8. The method of claim 1, wherein the firstsub-band and the second sub-band comprise resource blocks of a bandwidthpart.
 9. The method of claim 1, wherein the first sub-band and thesecond sub-band are adjacent.
 10. The method of claim 9, wherein the oneor more first resource elements and the one or more second resourceelements exclude one or more third resource elements of at least oneguard-band between the first sub-band and the second sub-band.
 11. Awireless device comprising: one or more processors; and memory storinginstructions that, when executed by the one or more processors, causethe wireless device to: receive configuration parameters of periodicradio resources of a configured uplink grant, wherein the periodic radioresources comprise: one or more first resource elements of a firstsub-band; and one or more second resource elements of a second sub-band;multiplex: a first configured grant uplink control information (CG-UCI)based on the one or more first resource elements; and a second CG-UCIbased on the one or more second resource elements, wherein the secondCG-UCI is based on a repetition of the first CG-UCI; and transmit, viathe periodic radio resources and based on one or more listen-before-talk(LBT) procedures performed on the first sub-band and the secondsub-band, at least one of the first CG-UCI and the second CG-UCI. 12.The wireless device of claim 11, wherein multiplexing a CG-UCI comprisesmultiplexing control bits for the CG-UCI onto data bits for a physicaluplink shared channel (PUSCH), and a length of the control bits isdetermined based on a number of resource elements that can be used fortransmission of the CG-UCI.
 13. The wireless device of claim 12, whereinthe instructions, when executed by the one or more processors, furthercause the wireless device to determine: based on a first frequencyoffset and a number of the one or more first resource elements, a firstlength of first control bits for the first CG-UCI; and based on a secondfrequency offset and a number of the one or more second resourceelements, a second length of second control bits for the second CG-UCI.14. The wireless device of claim 12, wherein the instructions, whenexecuted by the one or more processors, further cause the wirelessdevice to transmit the PUSCH via the periodic radio resources of theconfigured uplink grant and based on the one or more LBT proceduresperformed on the first sub-band and the second sub-band.
 15. Thewireless device of claim 14, wherein the first CG-UCI and the secondCG-UCI comprise at least one of: one or more hybrid automatic repeatrequest (HARD) process identifiers of the PUSCH; one or more indicatorsindicating whether the PUSCH corresponds to new data; one or moreredundancy versions of the PUSCH; and channel occupancy timeinformation.
 16. The wireless device of claim 11, wherein thetransmission comprises transmitting, in response to the one or more LBTprocedures indicating the first sub-band and the second sub-band areidle: the first CG-UCI via the first sub-band; and the second CG-UCI viathe second sub-band.
 17. The wireless device of claim 11, wherein theinstructions, when executed by the one or more processors, further causethe wireless device to, in response to the one or more LBT proceduresindicating the first sub-band is occupied and the second sub-band isidle: not transmit the first CG-UCI via the first sub-band; and transmitthe second CG-UCI via the second sub-band.
 18. The wireless device ofclaim 11, wherein the first sub-band and the second sub-band compriseresource blocks of a bandwidth part.
 19. The wireless device of claim11, wherein the first sub-band and the second sub-band are adjacent. 20.A system comprising: a base station comprising: one or more processors;and memory storing instructions that, when executed by the one or moreprocessors, cause the base station to transmit configuration parametersof periodic radio resources of a configured uplink grant, wherein theperiodic radio resources comprise: one or more first resource elementsof a first sub-band; and one or more second resource elements of asecond sub-band; and a wireless device comprising: one or moreprocessors; and memory storing instructions that, when executed by theone or more processors, cause the wireless device to: receive theconfiguration parameters; multiplex: a first configured grant uplinkcontrol information (CG-UCI) based on the one or more first resourceelements; and a second CG-UCI based on the one or more second resourceelements, wherein the second CG-UCI is based on a repetition of thefirst CG-UCI; and transmit, via the periodic radio resources and basedon one or more listen-before-talk (LBT) procedures performed on thefirst sub-band and the second sub-band, at least one of the first CG-UCIand the second CG-UCI.